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)

</defaultSyntaxesReplacements>

<matchingRule>integerMatch</matchingRule>

<matchingRule>numericStringMatch</matchingRule>

</subRule>

</matchingRules>

</matchingRulesReplacements>

<desc>IA5 String syntax.</desc>

<desc>Active Directory IA5 String LDAP Syntax.</desc>

</equivSyntax>

<desc>Directory String syntax.</desc>

</subSyntax>

</syntaxes>

</syntaxesReplacements>

</mappingPolicies>

If any mapping rules or the syntax used by an attribute type are not supported on the LDAP server, the

ldapschema utility checks if the appropriate substitution rule is speciﬁed in the

/etc/opt/ldapux/schema/map-rules.xml

ﬁle. If it is speciﬁed, ldapschema locates the ﬁrst

available matching rule or syntax supported on the LDAP server, and uses it in the attribute type deﬁnition

instead. If the substitution rule is not speciﬁed, or if the substitution matching rules or syntaxes are not

supported on the LDAP server,

ldapschema checks if the default substitution can be used.

Attributes vendor, versionGreaterOrEqual

, and versionLessThan can be used to specify

directory-speciﬁc information stored in

tags. If the default substitution is supported on the LDAP server, it is used in the attribute type deﬁnition

instead. If even the default substitution is not supported on the LDAP server, the attribute type cannot be

added to the LDAP directory server schema.

For example, an attribute type with IA5String syntax

(1.3.6.1.4.1.1466.115.121.1.26)

being installed on ADS, where this syntax oid is not supported.

ldapschema will try using the ﬁrst

equivalent or substitution syntax supported by the target LDAP server as speciﬁed in

/etc/opt/ldapux/schema/map-rules.xml

ﬁle. The speciﬁed equivalent syntax 2.5.5.5 with

oMSyntax value of 22 is supported on ADS and will be used in place of the original syntax value when

installing this attribute type deﬁnition on ADS.

As another example, for instance, attribute type with a Boolean equality matching rule is being installed

on the LDAP server where this matching rule is not supported. Since no substitution policy is speciﬁed for

this matching rule in the example above, the default substitution matching rule, caseIgnoreMatch,

would be used instead, if the LDAP server supports it. If the LDAP server does not support caseIg-

noreMatch

, that attribute type cannot be installed on the LDAP server, unless its deﬁnition is modiﬁed

to use another supported equality matching rule.

If the -s option is speciﬁed, syntax substitution in attribute types is disabled. Any attribute types with

unsupported LDAP syntaxes will not be added to the LDAP directory server schema. The -m option dis-

ables matching rule substitution. Any attribute types with unsupported matching rules will not be added to

the LDAP directory server schema.

EXAMPLES

To query the status of RFC 3712 schema on the Red Hat Directory Server 7.1, execute the following com-

mand:

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