Object Identifiers (Oids) - Red Hat DIRECTORY SERVER 8.1 - SCHEMA Reference

Chapter 1. About Directory Server Schema
Schema File
30ns-common.ldif
50ns-admin.ldif
50ns-certificate.ldif
50ns-directory.ldif
50ns-mail.ldif
50ns-value.ldif
50ns-web.ldif
60autofs.ldif
60eduperson.ldif
60mozilla.ldif
60nss-ldap.ldif
60pam-plugin.ldif
60pureftpd.ldif
60rfc2739.ldif
60rfc3712.ldif
60sabayon.ldif
60sudo.ldif
60trust.ldif
99user.ldif
Table 1.2. Schema Files

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
6
Purpose
Common schema.
Schemas used by the Administration Server.
Schemas used by Red Hat Certificate System.
Schema used by legacy Directory Server 4.x
servers.
Schema for mail servers.
Schema for value items in Directory Server.
Schema for web servers.
Object classes for automount configuration;
this is one of several schema files used for NIS
servers.
Schema elements for education-related people
and organization entries.
Schema elements for Mozilla-related user
profiles.
Schema elements for GSS-API service names.
Schema elements for integrating directory
services with PAM modules.
Schema elements for defining FTP user
accounts.
Schema elements for calendars and vCard
properties.
Schema elements for configuring printers.
Schema elements for defining sabayon user
entries.
Schema elements for defining sudo users and
roles.
Schema elements for defining trust relationships
for NSS or PAM.
Custom schema elements added through the
Directory Server Console.