Page created: 4 Feb 2020 |
Page updated: 22 Jul 2020
The Basic Properties section displays the standard elements in schema definition.
|Specifies the globally unique name.
|Specifies an optional definition that describes the attribute and its contents. The analogous LDIF equivalent is "DESC".
|Specifies 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.
|Specifies the attribute syntax used. For example, the
userPassword attribute uses the User Password Syntax whereas
authPassword attribute uses the Authentication Password
|Specifies 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.
|Specifies any restriction on the value of the attribute.
The Extra Properties section provides additional auxiliary information associated with the attribute.
|Specifies any shortform alias names, if any. In theory, you could 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’ ).
|Specifies 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.
|Specifies the intended use of the attribute. Choices are the following:
|Specifies if the attribute can be modified by an authorized user.
|Specifies if the schema definition is obsolete or not.
|Specifies the associated matching rules for the attribute.