LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

ManualsBrandsHP ManualsSoftwareHP-UX LDAP-UX Integration Software

371

372

373

374

375

376

377

378

379

380

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

</equivSyntax>

<desc>Directory String syntax.</desc>

</subSyntax>

</syntaxes>

</syntaxesReplacements>

</mappingPolicies>

How ldapschema maps unsupported matching rules and LDAP syntaxes

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

the ldapschema utility verifies that the appropriate substitution rule is specified in the /etc/opt/

ldapux/map-rules.xml file. If it is specified, ldapschema locates the first available matching

rule or syntax supported on the LDAP server, and uses it in the attribute type definition instead. If

the substitution rule is not specified, or none of the substitution matching rules or syntaxes are

supported on the LDAP directory server, ldapschema verifies that the default substitution can be

used.

The “vendor”, “versionGreaterOrEqual” and “versionLessThan” XML attributes can be

used to specify directory-specific information stored in <defaultMatchingRule> and

<defaultSyntax> tags. If the default substitution is not supported on the LDAP server, the attribute

type cannot be added to the LDAP directory server schema.

Examples

For example, an attribute type with IA5String syntax (1.3.6.1.4.1.1466.115.121.1.26)

is installed on Windows ADS, where this IA5 String syntax is not supported. ldapschema will try

using the first specified equivalent or substitution syntax supported by the target LDAP directory

server. The specified equivalent syntax of 2.5.5.5 syntax with the oMSyntax value of 22 is

supported on windows ADS and will be used in place of the original syntax value.

As another example, assume an attribute type with a Boolean equality rule is being installed on

the LDAP server where this matching rule is not supported. Since no substitution policy is specified

for this matching rule in the preceding example, the default substitution matching rule,

caseIgnoreMatch, would be used instead, if the LDAP server supports it. If the LDAP server does

not support caseIgnoreMatch, that attribute type cannot be installed on the LDAP server, unless

its definition is modified to use another supported equality matching rule.

If the –s– option is specified in the ldapsechema tool, syntax substitution in attribute types is

disabled. Any attribute types with unsupported LDAP syntaxes are not added to the LDAP directory

server schema. The –m– option with the ldapschema tool disables matching rule substitution. Any

attribute types with unsupported matching rules are not added to the LDAP directory server schema.

9.5.8 Return values from ldapschema

The ldapschema tool returns the following values:

0 The operation is successful.

–1 The operation fails.

In addition, ldapschema prints to STDOUT the overall status of the schema being queried or

extended. Based on the schema status, any combination of the following messages is displayed.

Detailed explanations of each message are specified in the square brackets following the message

body text.

374 Command and tool reference