HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

551

552

553

554

555

556

557

558

559

560

ldapschema(1) ldapschema(1)

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 6.2 through 7.0, the

X-ORIGIN ﬂag for the sampleAttribute will be set to

’Custom Schema’ as speciﬁed in the

dsSpecific ﬁeld. On Red Hat Directory Server 6.1 and ear-

lier, or 7.1 and later, the

X-ORIGIN ﬂag for sampleAttribute will be set to the value speciﬁed in the

<schemaSource> tag.

On Active Directory Server 2000, the sampleAttribute is added using the same display name as speciﬁed 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 speciﬁc information can also be speciﬁed in the object class deﬁnitions.

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-speciﬁc attributes and values speciﬁed using <dsSpecific> ﬁelds are not vali-

dated. Make sure the values speciﬁed in these ﬁelds are legitimate and adhere to the LDAP directory

server rules. The ﬁeld value must be speciﬁed exactly as it is to appear in the attribute type or object class

deﬁnition, using single and double quotes as applicable.

<dsSpecific> attributes and values override

the default attribute type and object class conﬁgurations. For instance, on Active Directory Server the

isDefunct setting by default is set to FALSE. However, specifying

</dsSpecific>

will override this default setting and will result in the element being defunct (that is, obsolete).

LDAP DIRECTORY SERVER DEFINTION FILE

In order to properly install new attribute types on the LDAP directory server schema, the ldapschema

utility needs to determine whether the LDAP server supports the matching rules and LDAP syntaxes used

by the new attribute type deﬁnitions. The ldapschema utility performs an LDAP search for supported

552 Hewlett-Packard Company − 8 − HP-UX 11i Version 2: December 2007 Update