|Definition:||An explanation of the exact meaning of the attribute. For attributes that are not unique to the Texas A&M LDAP directory, the definition is an explanation of the meaning of the attribute in the Texas A&M directory.|
|Attribute Name:||Name of the attribute. More that one name can be associated with an attribute.|
|OID:||Object identifier for the attribute. The object identifier is composed of a string of dotted numbers that uniquely identifies the attribute worldwide. The Internet Assigned Numbers Authority (IANA) governs the assignment of OIDs.|
|URN:||Uniform resource name for the attribute. The uniform resource name has the syntax urn:NID:NSS where NID is the namespace identifier, and NSS is the namespace specific string. The namespace identifier determines the syntactic interpretation of the namespace specific string.|
|Multiple Values:||Denotes whether or not the attribute is allowed to store more than one value.|
|Format:||The encoding rules used for storing and transmitting values of the attribute type. The number enclosed by the curly braces specifies the minimum recommended maximum length of the attribute's value that a server should support.|
|Search Syntax:||The grammatical rules and structural patterns governing searches on attribute values.|
|Controlled Vocabulary:||A listing of allowed values. For attributes that have a controlled vocabulary, the definitions of the values will be provided as well.|
|Source:||Rules governing population of the attribute.|
|Directory URL:||Directory server URL.|
|Object Class:||The object class that the attribute is associated with. It is possible for an attribute to belong to multiple object classes.|
Denotes whether or not an attribute must be present in an entry. In this case,
"present" means "possesses at least one value".
It is the object classes that specify whether or not attributes are required or optional. For attributes associated with multiple object classes, they may be optional for one and required by another.
Attributes may be indexed to optimize searches, similar to the indexes used by a
relational database management system. LDAP supports four types of indexes.
However, not all attributes support all four index types. Each index type
corresponds to one of the matching rules defined in the directory schema.
Indexes the information for an approximate, or phonetic, match of an attribute value.
Indexes the information necessary to perform an exact match of an attribute value. The match may be case-sensitive or whitespace-sensitive, depending on the matching rules defined in the attribute syntax.
Indexes the information necessary to determine if an attribute has any value at all. If an attribute does not possess a value, then the attribute is not present in the directory entry.
Indexes the information necessary to perform a simple substring match on attribute values.
Denotes who has access
Access control List (ACL) terminology for these parameters:
* Matches any connected user, including anonymous connection
self The DN of the currently connected user, assuming he has been successfully authenticated by a previous bind request.
anonymous Nonauthenticated user connections
users Authenticated user connections
regular expression matches a DN or SASL identity
(Higher levels possess all the capabilities of the lower levels.)
write Access to update attribute values (e.g., Change this telephoneNumber to 555-2345).
read Access to read search results (e.g., Show me all the entries with a telephoneNumber of 555*).
search Access to apply search filters (e.g., Are there any entries with a telephoneNumber of 555*).
compare Access to compare attributes (e.g., Is your telephoneNumber 555-1234?)
auth Access to bind (authenticate).
none No access.
The What defines the entry and attributes to which the ACL should apply. It is composed of three basic parts, all of which are optional. If none of these components are present, a single asterisk is used as a placeholder to include everything.
|Usage:||Example(s) of known uses of the attribute values.|
|Example(s):||Example(s) of values for the attribute. To make the example more helpful, the values are representative of a full-time staff person taking a class.|