ldapschema.1 (2010 09)
l
ldapschema(1) ldapschema(1)
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 only="ads"
Line 5: versionGreaterOrEqual="2003">my-sample-attribute</displayName>
Line 6: <equality>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>
On Red Hat Directory Server 7.1 and later, and on HP-UX Directory Server, the
X-ORIGIN flag for sam-
pleAttribute will be set to the value specified in the
<schemaSource>
tag.
On Active Directory Server 2000, the sampleAttribute is added using the same display name as specified
by the
<name> value, with rangeLower attribute set to 256, and systemOnly attribute set to TRUE
.
On Active Directory Server 2003, the sampleAttribute is added using my-sample-attribute display name,
with
rangeLower attribute set to 512, and systemOnly attribute set to FALSE, which is the default
value.
Also, since
1.3.6.1.4.1.1466.115.121.1.15
syntax is not supported on the ADS, it is mapped to
the corresponding Directory String syntax supported on ADS, which is
attributeSyntax=2.5.5.12
oMSyntax=64. See the MAPPING UNSUPPORTED MATCHING RULES AND LDAP SYNTAXES sec-
tion for details.
Directory specific information can also be specified in the object class definitions.
Line 1: <objectClassDefinition>
Line 2: <oid>1.23.456.7.89101112.1.314.1.51.7</oid>
Line 3: <name>sampleObject</name>
Line 4: <must only="ads">serverRole</must>
Line 5: <must not="ads">userPassword</must>
Line 6: <may>sampleAttribute</may>
Line 7: <dsSpecific vendor="ads">
Line 8: <field attr="systemOnly">TRUE</field>
Line 9: </dsSpecific>
Line 10: </objectClassDefinition>
On Active Directory Server, this object class has a mandatory attribute type serverRole and an optional
attribute sampleAttribute. On all other types of directory servers, this object class has a mandatory attri-
bute type userPassword and an optional attribute sampleAttribute. Also, on Active Directory Server this
object class has the
systemOnly attribute set to TRUE.
WARNING: Directory-specific attributes and values specified using
<dsSpecific> fields are not vali-
dated. Make sure the values specified in these fields are legitimate and adhere to the LDAP directory
server rules. The field value must be specified exactly as it is to appear in the attribute type or object
class definition, using single and double quotes as applicable.
<dsSpecific> attributes and values
override the default attribute type and object class configurations. For instance, on Active Directory
Server the isDefunct setting by default is set to FALSE. However, specifying
<dsSpecific vendor="ads">
<field attr="isDefunct">TRUE</field>
</dsSpecific>
will override this default setting and will result in the element being defunct (i.e. obsolete).
8 Hewlett-Packard Company − 8 − HP-UX 11i v3: June 2010 Web Release