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

l
ldapschema(1) ldapschema(1)
<rdn> Optional. Defines the recommended attribute to use for the Relative Distinguished Name
(RDN) for new entries created with this object class. Currently,
<rdn> applies only to
Active Directory Server (ADS). At most one RDN can be specified.
extendAuxiliaryClass
Optional, applies to AUXILIARY object classes only. This tag is used to extend an object
class already defined in the LDAP server schema with this new AUXILIARY object class.
Currently, <extendAuxiliaryClass>
applies only to Active Directory Server (ADS)
to include the new AUXILIARY class as an
auxiliaryClass in the definition of another
object class already defined in the LDAP server schema.
<dsSpecific>
Optional, use to specify any directory-specific information about the attribute type. See the
SPECIFYING DIRECTORY-SPECIFIC INFORMATION section for details.
Each object class definition must meet the following conditions in order to be added to the LDAP directory
server schema:
• The object class has a numeric OID which adheres to RFC 2252 format specification.
• The object class has at least one name. Each name must adhere to RFC 2252 format specification.
• No other object classes in the schema definition file or on the LDAP directory server have the same OID
or any of its name values.
• The super-class(es) used by this object classes are defined.
• The attribute(s) used by this object classes are defined.
• The inheritance hierarchy has no cycles (no circular dependencies exist in the super-class/sub-class rela-
tionships).
• An
ABSTRACT object class can specify only ABSTRACT object class(es) as its super-class(es).
• An AUXILIARY object class can specify ABSTRACT or AUXILIATY object class(es) as its super-
class(es).
• A STRUCTURAL object class can specify ABSTRACT or STRUCTURAL object class(es) as its super-
class(es).
Predefined Schema Definition Files
The following LDAP schema definition files are delivered with the LDAP-UX product:
• /etc/opt/ldapux/schema/rfc2256.xml
• /etc/opt/ldapux/schema/rfc2307.xml
• /etc/opt/ldapux/schema/rfc2307-bis.xml
• /etc/opt/ldapux/schema/rfc2926.xml
• /etc/opt/ldapux/schema/rfc3712.xml
These files are provided as examples to demonstrate how to define new LDAP schema definition files to use
with the ldapschema utility. Since these files define attribute types and object classes that come pre-
installed on most LDAP directory servers they are not intended for extending the LDAP directory server
schema. Instead, these files are provided for reference when creating the new schema definition files to
query and extend the LDAP directory server schema with the new attribute type and object class
definitions.
SPECIFYING DIRECTORY-SPECIFIC INFORMATION
Attribute type and object class definitions can be extended with directory-specific information using the
<dsSpecific> tag. This is useful to maintain a single schema definition file for different types and ver-
sions of LDAP directory servers. The following example illustrates how a single attribute type definition
can be altered to support Red Hat Directory Server and Active Directory Server directory server specific
definitions simultaneously.
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>
HP-UX 11i Version 2: December 2007 Update − 7 − Hewlett-Packard Company 551