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)

<oid> Required. Exactly one numeric id must be speciﬁed.

<name> Required. At least one matching rule type name must be speciﬁed. Do not use quotes

around the name values.

<desc> Optional. At most one description can be speciﬁed.

<obsolete> Optional, use only if applicable. Obsolete matching rules cannot be used in deﬁnitions of

any other attribute types. At most one obsolete ﬂag can be speciﬁed.

<syntax> Required. Speciﬁed LDAP syntax must also be supported on the LDAP directory server.

At most one LDAP syntax can be speciﬁed per matching rule deﬁnition.

Only syntaxes and matching rules fully supported by the LDAP directory server can be speciﬁed in this ﬁle.

Attributes vendor, versionGreaterOrEqual

, and versionLessThan can be used to specify

directory-speciﬁc information.

See

/etc/opt/ldapux/schema/schema-ads.xml

for an example of LDAP directory server

deﬁnition ﬁles.

MAPPING UNSUPPORTED MATCHING RULES AND LDAP SYNTAXES

If matching rules and/or LDAP syntaxes used in attribute type deﬁnitions in the schema deﬁnition ﬁle are

not supported on the LDAP directory server, they need to be mapped to use alternate matching rules and

syntaxes the LDAP server does support.

The matching rules are speciﬁed in

<equality> , <ordering> ,or<substr> tags in the attribute

type deﬁnition. The LDAP syntax is speciﬁed in the <syntax> tag. The mapping rules that determine

how the matching rules and syntaxes are replaced are speciﬁed in

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

ﬁle. If ldapschema cannot successfully map the

attribute’s matching rules and syntax,

ldapschema

will not be able to add the attribute type to the LDAP

directory server schema.

The purpose of the mapping rules ﬁle is to allow an LDAP schema to be installed on an LDAP directory

server even if some of matching rules and LDAP syntaxes used in the deﬁnition of that schema are not sup-

ported by the directory server. File

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

uses the follow-

ing mapping rules guideline:

• map more restrictive syntaxes to less restrictive syntaxes

• map more speciﬁc matching rules to less speciﬁc matching rules

For example, the Integer syntax contains a subset of characters of the IA5 string syntax. Therefore, it is

acceptable to map the Integer syntax to the IA5 string syntax, since the IA5 string syntax is a superset of

the Integer syntax.

The following example illustrates a sample

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

ﬁle.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE mappingPolicies SYSTEM "schema.dtd">

<matchingRule>caseIgnoreMatch</matchingRule>

</defaultMatchingRule>

</defaultMatchingRulesReplacements>

<desc>Active Directory String syntax.</desc>

</defaultSyntax>

<desc>Directory String syntax.</desc>

</defaultSyntax>

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