HP-UX Directory Server 8.1 schema reference

Table 1-2 Schema files (continued)
PurposeSchema file
Schemas used by Certificate System.50ns-certificate.ldif
Schema used by legacy Directory Server 4.x servers.50ns-directory.ldif
Schema for mail servers.50ns-mail.ldif
Schema for value items in Directory Server.50ns-value.ldif
Schema for web servers.50ns-web.ldif
Object classes for automount configuration; this is one of several schema files used for NIS
servers.
60autofs.ldif
Schema elements for education-related people and organization entries.60eduperson.ldif
Schema elements for Mozilla-related user profiles.60mozilla.ldif
Schema elements for GSS-API service names.60nss-ldap.ldif
Schema elements for integrating directory services with PAM modules.60pam-plugin.ldif
Schema elements for defining FTP user accounts.60pureftpd.ldif
Schema elements for calendars and vCard properties.60rfc2739.ldif
Schema elements for configuring printers.60rfc3712.ldif
Schema elements for defining sabayon user entries.60sabayon.ldif
Schema elements for defining sudo users and roles.60sudo.ldif
Schema elements for defining trust relationships for NSS or PAM.60trust.ldif
Custom schema elements added through the Directory Server Console.99user.ldif
1.3 Object identifiers (OIDs)
All schema elements have object identifiers (OIDs) assigned to them, including attributes and
object classes. An OID is a sequence of integers, usually written as a dot-separated string. All
custom attributes and classes must conform to the X.500 and LDAP standards.
CAUTION:
If an OID is not specified for a schema element, Directory Server automatically uses
ObjectClass_name-oid and attribute_name-oid. However, using text OIDs instead of
numeric OIDs can lead to problems with clients, server interoperability, and server behavior,
assigning a numeric OID is strongly recommended.
OIDs can be built on. The base OID is a root number which is used for every schema element for
an organization, then schema elements can be incremented from there. For example, a base OID
could be 1. The company then uses 1.1 for attributes, so every new attribute has an OID of
1.1.x. It uses 1.2 for object classes, so every new object class has an OID of 1.2.x.
For Directory Server-defined schema elements, the base OIDs are as follows:
• The Netscape base OID is 2.16.840.1.113730.
• The Directory Server base OID is 2.16.840.1.113730.3.
• All Netscape-defined attributes have the base OID 2.16.840.1.113370.3.1.
• All Netscape-defined object classes have the base OID 2.16.840.1.113730.3.2.
For more information about OIDs or to request a prefix, go to the Internet Assigned Number
Authority (IANA) website at http://www.iana.org/.
1.3 Object identifiers (OIDs) 13