The following table details the standard elements in schema definition.

Basic Properties of Attributes
Attributes Description


The globally unique name


An optional definition that describes the attribute and its contents

The LDIF equivalent is DESC.


The object identifier assigned to the schema definition

You can obtain a specific OID for your company that allows you to define your own object classes and attributes from IANA or ANSI.


The attribute syntax used

For example, the userPassword attribute uses the User Password Syntax whereas the authPassword attribute uses the Authentication Password Syntax.


The schema definition’s parent or supertype, if any

The analogous LDIF equivalent is SUP.


Specifies if the attribute can appear more than once in its containing object class

Required By Class

Specifies any object classes that require the attribute

Allowed By Class

Specifies any object classes that can optionally use the attribute

Value Restrictions

Specifies any restriction on the value of the attribute

The Additional Properties table details auxiliary information associated with the attribute.

Attributes Description


Any shortform alias names, if any

You can have any number of shortform names as long as they are all unique. The analogous LDIF equivalent appears as the secondary element with the NAME element. For example, NAME, sn, surname.


The origin of the schema definition

Typically, it could refer to a specific RFC or company.

Stored in File

Specifies the schema file that stores the definition in the <server-root>/config/schema folder


The intended use of the attribute

The choices are:

  • userApplications
  • directoryOperation
  • distributedOperation
  • dSAOperation


Specifies if the attribute can be modified by an authorized user


Specifies if the schema definition is obsolete or not

Matching Rules

Specifies the associated matching rules for the attribute