Red Hat Directory Server 8.0 Administrator's Guide

For example, a CoS template entry for generating a department number appears as follows:
dn: cn=data,dc=example,dc=com
objectclass: top
objectclass: extensibleObject
objectclass: cosTemplate
departmentNumber: 71776
cosPriority: 0
This template entry contains the value for the departmentNumber attribute. It has a priority of
zero, meaning this template takes precedence over any other conflicting templates that define a
different departmentNumber value.
Templates that contain no cosPriority attribute are considered the lowest priority. Where two
or more templates are considered to supply an attribute value and they have the same (or no)
priority, a value is chosen arbitrarily. The behavior for negative cosPriority values is not
defined in Directory Server; do not enter negative values. Also, the cosPriority attribute is not
supported by indirect CoS.
The following sections provide examples of template entries along with examples of each type
of CoS definition entry.
• Section 2.3.3, “Example of a Pointer CoS”
• Section 2.3.4, “Example of an Indirect CoS”
• Section 2.3.5, “Example of a Classic CoS”
2.3.3. Example of a Pointer CoS
Example Corporation's administrator is creating a pointer CoS that shares a common postal
code with all entries in the dc=example,dc=com tree.
1. Add a new pointer CoS definition entry to the dc=example,dc=com suffix using ldapmodify:
ldapmodify -a -D "cn=directory manager" -w secret -h host -p 389
The ldapmodify utility binds to the server and prepares it to add information to the
configuration file.
2. Next, add the pointer CoS definition to the dc=example,dc=com root suffix.
dn: cn=pointerCoS,dc=example,dc=com
objectclass: top
objectclass: cosSuperDefinition
objectclass: cosPointerDefinition
cosTemplateDn: cn=exampleUS,ou=data,dc=example,dc=com
Chapter 5. Managing Entries with Roles, Class of Service, and Views
158