LDAP-UX Client Services B.04.10 with Microsoft Windows Active Directory Server Administrator's Guide

Defining Directory Specific Information
Attribute type and object class definitions can be extended with directory-specific information
using the <dsSpecific> tag. This is useful to maintain a single schema definition file for
different types and versions of LDAP directory servers.
An Example of Defining Directory Specific Information in the Attribute Type Definition
This section takes an example to illustrate how directory specific information can be specified
in a single attribute type definition to support Netscape/Red Hat Directory Server and Windows
Active Directory Server specific definitions simultaneously.
The following is an example of the attribute type definition with directory specific information
using the <dsSpecific> tag:
Line 1: <attributeTypeDefinition>
Line 2: <oid>1.23.456.7.89101112.1.314.1.51.6<oid>
Line 3: <name>sampleAttribute</name>
Line 4: <displayName vendor="ads">
LINE 5: versionGreaterOrEqual="2003">my-sample-attribute</displayName>
LINE 6: <equlaity>caseIgnoreMatch</equality>
Line 7: <syntax>1.3.6.1.4.1.1466.115.121.1.15</syntax>
Line 8: <dsSpecific vendor="rhds" versionGreaterorEqual="6.2"
Line 9: versionLessThan="7.1"
Line 10: <field attr="X-ORIGIN">'Custom Schema'</field>
Line 11: </dsSpecific>
Line 12: <dsSpecific vendor="ads" versionLessThan="2003">
Line 13: <field attr="systemOnly">TRUE</field>
Line 14: <field attr="rangeLower">256</field>
Line 15: </dsSpecific>
Line 16: <dsSpecific vendor="ads" versionGreaterOrEqual="2003">
Line 17: <field attr="rangeLower">512</field>
Line 18: </dsSpecific>
Line 19: </attributeTypeDefinition>
For the above example, on Red Hat Directory Server 6.2 through 7.0, the X-ORIGIN flag for
sampleAttribute will be set to ‘Custom Schema’ as specified in the dsSpecific field. On
Red Hat Directory Server 6.1 and earlier, or 7.1 and later, the X-ORIGIN flag for
sampleAttribute will be set to the value specified in the <schemaSource>
On Active Directory Server 2000, the sampleAttribute is added using the same display name
as specified by the <name> value, with the rangeLower attribute set to 256, and the systemOnly
attribute set to TRUE.
On Active Directory Server 2003, the sampleAttribute is added using
“my-sample-attribute” display name, with the rangeLower attribute set to 512, and
the systemOnly attribute set to FALSE, which is the default value.
Table C-7 Directory Specific Information
ADS 2003ADS 2000RHDS 7.1RHDS 6.2–7.0Attribute
sampleAttributesampleAttributesampleAttributesampleAttribute
Name
my-sample-attributesampleAttribute
N/AN/ADisplay Name
N/AN/AAs Specified in
<schemaSource>
'Custom Schema'
X-ORIGIN
FALSE (default)TRUEN/AN/A
systemOnly
512256N/AN/A
rangeLower
Also, the 1.3.6.1.4.1.1466.115.121.1.15 syntax is not supported on the Windows ADS, it is mapped
to the corresponding Directory String syntax supported on Windows ADS, which is
attributeSyntax = 2.5.5.12, oMSyntax=64. See “Mapping Unsupported Matching Rules
and LDAP Syntaxes” (page 174) section for details.
170 Command, Tool, Schema Extension Utility, and Migration Script Reference