Lines Matching refs:attribute
80 3.3. The 'objectClass' attribute ...............................18
294 identify like kinds of objects (e.g., attribute type descriptions,
344 Section 2.5 discusses attribute descriptions.
378 An attribute is an attribute description (a type and zero or more
379 options) with one or more associated values. An attribute is often
380 referred to by its attribute description. For example, the
381 'givenName' attribute is the attribute that consists of the attribute
382 description 'givenName' (the 'givenName' attribute type [RFC4519] and
385 The attribute type governs whether the attribute can have multiple
387 values of that attribute, and other functions. Options indicate
390 Attribute values conform to the defined syntax of the attribute type.
399 No two values of an attribute may be equivalent. Two values are
401 the equality matching rule of the attribute type. Or, if the
402 attribute type is defined with no equality matching rule, two values
406 For example, a 'givenName' attribute can have more than one value,
408 'givenName' attribute cannot hold both "John" and "JOHN", as these
409 are equivalent values per the equality matching rule of the attribute
412 Additionally, no attribute is to have a value that is not equivalent
413 to itself. For example, the 'givenName' attribute cannot have as a
416 Undefined per this attribute's equality matching rule.
418 When an attribute is used for naming of the entry, one and only one
419 value of the attribute is used in forming the Relative Distinguished
428 [X.501], is composed of an unordered set of one or more attribute
429 value assertions (AVA) consisting of an attribute description with
430 zero options and an attribute value. These AVAs are chosen to match
431 attribute values (each a distinguished value) of the entry.
521 an attribute allowed by its superclass as being required. If an
522 attribute is a member of both sets, it is required to be present.
634 An attribute description is composed of an attribute type (see
635 Section 2.5.1) and a set of zero or more attribute options (see
638 An attribute description is represented by the ABNF:
645 where <attributetype> identifies the attribute type and each <option>
646 identifies an attribute option. Both <attributetype> and <option>
652 Examples of valid attribute descriptions:
658 An attribute description with an unrecognized attribute type is to be
659 treated as unrecognized. Servers SHALL treat an attribute
660 description with an unrecognized attribute option as unrecognized.
661 Clients MAY treat an unrecognized attribute option as a tagging
664 All attributes of an entry must have distinct attribute descriptions.
668 An attribute type governs whether the attribute can have multiple
670 values of that attribute, and other functions.
679 If no equality matching is specified for the attribute type:
681 - the attribute (of the type) cannot be used for naming;
682 - when adding the attribute (or replacing all values), no two
684 - individual values of a multi-valued attribute are not to be
686 - attribute value assertions (such as matching in search filters
691 evaluate attribute value assertions concerning the attribute type.
694 The attribute type indicates whether the attribute is a user
695 attribute or an operational attribute. If operational, the attribute
696 type indicates the operational usage and whether or not the attribute
700 An attribute type (a subtype) may derive from a more generic
701 attribute type (a direct supertype). The following restrictions
710 An attribute description consisting of a subtype and no options is
711 said to be the direct description subtype of the attribute
715 Each attribute type is identified by an object identifier (OID) and,
720 There are multiple kinds of attribute description options. The LDAP
735 Not all options can be used in conjunction with all attribute types.
736 In such cases, the attribute description is to be treated as
739 An attribute description that contains mutually exclusive options
748 the directory, how new kinds of options affect transfer of attribute
749 values, and how new kinds of options are treated in attribute
761 Attributes held in the directory can have attribute descriptions with
765 An attribute description with N tagging options is a direct
766 (description) subtype of all attribute descriptions of the same
767 attribute type and all but one of the N options. If the attribute
768 type has a supertype, then the attribute description is also a direct
769 (description) subtype of the attribute description of the supertype
777 An attribute description can be the direct subtype of zero or more
778 other attribute descriptions as indicated by attribute type subtyping
779 (as described in Section 2.5.1) or attribute tagging option subtyping
781 used to form hierarchies of attribute descriptions and attributes.
796 attribute description (a direct reference to the attribute) or a
797 more generic attribute description (an indirect reference).
803 attribute description; a filter item so specified is evaluated for
812 available. An attribute value shall always be returned as a value
813 of its own attribute description.
815 All of the attribute descriptions in an attribute hierarchy are
819 An attribute value stored in an object or alias entry is of
820 precisely one attribute description. The description is indicated
824 specification that an attribute is required is fulfilled if the entry
825 contains a value of an attribute description belonging to an
826 attribute hierarchy where the attribute type of that description is
827 the same as the required attribute's type. That is, a "MUST name"
831 attribute description belonging to an attribute hierarchy where the
832 attribute type of that description is either explicitly included in
849 model, all of the attribute descriptions in an attribute hierarchy
861 attribute (known as the 'aliasedEntryName' attribute in X.500), a
872 the corresponding 'aliasedObjectName' attribute. The process may
916 The 'aliasedObjectName' attribute holds the name of the entry an
917 alias points to. The 'aliasedObjectName' attribute is known as the
918 'aliasedEntryName' attribute in X.500.
973 formed from a value of the 'cn' (commonName) attribute [RFC4519] (as
976 3.3. The 'objectClass' attribute
978 Each entry in the DIT has an 'objectClass' attribute.
987 The 'objectClass' attribute specifies the object classes of an entry,
990 Values of this attribute can be modified by clients, but the
991 'objectClass' attribute cannot be removed.
994 this attribute to prevent the basic structural class of the entry
1004 Servers SHALL restrict modifications of this attribute to prevent
1015 class 'x-b' and the 'objectClass' attribute contains 'x-a' and 'x-b',
1016 an attempt to delete only 'x-b' from the 'objectClass' attribute is
1027 A directory operational attribute is used to represent operational
1033 A DSA-shared operational attribute is used to represent information
1036 A DSA-specific operational attribute is used to represent information
1077 This attribute appears in entries that were added using the protocol
1092 This attribute appears in entries that were added using the protocol
1109 This attribute appears in entries that have been modified using the
1132 This attribute appears in entries that have been modified using the
1149 This attribute indicates the structural object class of the entry.
1162 This attribute indicates the structure rule governing the entry.
1193 be matched in attribute value and matching rule assertions.
1200 - prevent the addition of attribute-types to an entry
1204 - prevent the addition of an attribute value of a syntax not
1205 matching that defined for the attribute-type (e.g., a printable
1240 by which an attribute is known, its syntax, associated matching
1241 rules, whether it is an operational attribute and if so its
1242 type, whether it is a collective attribute, whether it is
1244 derived from another attribute type;
1321 [ SP "MUST" SP oids ] ; attribute types
1322 [ SP "MAY" SP oids ] ; attribute types
1336 MUST and MAY specify the sets of required and allowed attribute
1377 <numericoid> is object identifier assigned to this attribute type;
1379 attribute type;
1381 OBSOLETE indicates this attribute type is not active;
1389 COLLECTIVE indicates this attribute type is collective
1391 NO-USER-MODIFICATION indicates this attribute type is not user
1393 USAGE indicates the application of this attribute type; and
1396 Each attribute type description must contain at least one of the SUP
1397 or SYNTAX fields. If no SYNTAX field is provided, the attribute type
1419 directoryOperation usage indicates that the attribute of this type is
1420 a directory operational attribute. distributedOperation usage
1421 indicates that the attribute of this type is a DSA-shared usage
1422 operational attribute. dSAOperation usage indicates that the
1423 attribute of this type is a DSA-specific operational attribute.
1426 attribute types in LDAP is discussed in [RFC3671].
1431 rules that can be used with that attribute type in an extensibleMatch
1433 attribute described in Section 4.1.4.
1439 bound of a value of this attribute.
1465 Matching rules are used in performance of attribute value assertions,
1496 A matching rule use lists the attribute types that are suitable for
1507 SP "APPLIES" SP oids ; attribute types
1526 APPLIES provides a list of attribute types the matching rule
1532 LDAP Syntaxes of (attribute and assertion) values are described in
1562 The list of precluded attributes cannot include any attribute listed
1590 An entry cannot include any attribute precluded by the governing
1609 [ SP "MUST" SP oids ] ; attribute types
1610 [ SP "MAY" SP oids ] ; attribute types
1611 [ SP "NOT" SP oids ] ; attribute types
1631 MUST, MAY, and NOT specify lists of attribute types that are
1695 and one or more attribute types to be used for naming (i.e., for the
1700 set of required attribute types, and a set of allowed attribute
1701 types. A particular attribute type cannot be in both sets.
1704 required attribute type and zero or more values from the allowed
1705 attribute types.
1718 SP "MUST" SP oids ; attribute types
1719 [ SP "MAY" SP oids ] ; attribute types
1733 All attribute types in the required ("MUST") and allowed ("MAY")
1761 (sub)entries including providing a 'subschemaSubentry' attribute in
1767 The value of the 'subschemaSubentry' attribute is the name of the
1787 The 'ldapSyntaxes' operational attribute may also be present in
1806 The following subsections provide attribute type definitions for each
1807 of schema definition attribute types.
1811 This attribute holds definitions of object classes.
1824 This attribute holds definitions of attribute types.
1837 This attribute holds definitions of matching rules.
1857 This attribute holds definitions of matching rule uses.
1870 This attribute holds definitions of LDAP syntaxes.
1883 This attribute lists DIT Content Rules that are present in the
1913 This attribute lists DIT Structure Rules that are present in the
1927 This attribute lists Name Forms that are in force.
1941 belong to it to hold any user attribute. The set of allowed
1942 attribute types of this object class is implicitly the set of all
1943 attribute types of userApplications usage.
1956 'subschemaSubentry' operational attribute. To read schema attributes
2001 naming context (or any subtree); each server has different attribute
2057 The root DSE may also include a 'subschemaSubentry' attribute. If it
2058 does, the attribute refers to the subschema (sub)entry holding the
2081 The 'altServer' attribute lists URIs referring to alternative servers
2085 any other servers that could be used, this attribute will be absent.
2098 The 'namingContexts' attribute lists the context prefixes of the
2103 gateway to a public X.500 directory) this attribute will be absent.
2105 the attribute will have a single value, and that value will be the
2108 This attribute may be used, for example, to select a suitable entry
2120 The 'supportedControl' attribute lists object identifiers identifying
2122 does not support any request controls, this attribute will be absent.
2144 The 'supportedExtension' attribute lists object identifiers
2147 this attribute will be absent.
2154 listed as values of this attribute.
2168 The 'supportedFeatures' attribute lists object identifiers
2171 attribute will be absent.
2193 The 'supportedLDAPVersion' attribute lists the versions of LDAP that
2205 The 'supportedSASLMechanisms' attribute lists the SASL mechanisms
2207 contents of this attribute may depend on the current session state.
2208 If the server does not support any SASL mechanisms, this attribute
2267 attribute type 'x-fubar' in a subschema.
2307 Servers MUST recognize all names of attribute types and object
2310 all the names of attribute types and object classes defined in
2343 Clients SHOULD NOT send attribute values in a request that are not
2609 Section 3.2.1 of RFC 2251 described an attribute as "a type with one
2610 or more associated values". In LDAP, an attribute is better
2611 described as an attribute description, a type with zero or more
2623 attribute.
2663 'subschemaSubentry' attribute within the root DSE. The previous
2664 specification stated that the 'subschemaSubentry' attribute held in
2666 by this server". This is inconsistent with the attribute's
2668 attribute [X.501]. It is also noted that a simple (possibly
2671 'subschemaSubentry' attribute of the root DSE refers to the
2727 specification of the semantics of attribute options appearing in NAME
2771 'governingStructureRule' operational attribute types were added.
2773 The attribute definition of 'subschemaSubentry' was corrected to list
2794 attribute type. This was integrated into Section 2.4.1 of this
2808 'aliasedObjectName' attribute type. This was integrated into Section