Attribute Syntax
The syntax of an attribute represents the kind of data it can hold; people with a programming background are probably more familiar with the term “data type.” Unlike attributes and classes, the supported syntaxes are not represented as objects in Active Directory. Instead, Microsoft has coded these syntaxes internally into Active Directory itself. Consequently, any new attributes you create in the schema must use one of the predefined syntaxes.
Whenever you create a new attribute, you must specify its syntax. To uniquely identify the syntax among the total set of 21 syntaxes, you must specify 2 pieces of information: the OID of the syntax and a so-called OM syntax. This pair of values must be set together and correctly correlate with Table 4-3. More than one syntax has the same OID, which may seem strange; and to distinguish between different syntaxes uniquely, you thus need a second identifier. This is the result of Microsoft requiring some syntaxes that X.500 did not provide. Table 4-3 shows the 21 expanded syntaxes, including the name of the syntax with alternate names followed in parentheses.
Table 4-3. Syntax definitions
|
Syntax |
OID |
OM syntax |
Description |
|---|---|---|---|
|
Undefined |
2.5.5.0 |
N/A |
Not a valid syntax |
|
Distinguished Name |
2.5.5.1 |
127 |
The Fully Qualified Domain Name (FQDN) of an object in Active Directory |
|
Object ID |
2.5.5.2 |
6 |
OID |
|
Case-sensitive string |
2.5.5.3 |
20 |
A string that differentiates between uppercase and lowercase |
|
Case-insensitive string |
2.5.5.4 ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access