Red Hat Directory Server 8.0 Administrator's Guide

cosAttribute: postalCode
3. Create the template entry.
dn: cn=exampleUS,ou=data,dc=example,dc=com
objectclass: top
objectclass: extensibleObject
objectclass: cosTemplate
postalCode: 44438
The CoS template entry (cn=exampleUS,ou=data,dc=example,dc=com) supplies the value
stored in its postalCode attribute to any entries located under the dc=example,dc=com suffix.
These entries are the target entries.
2.3.4. Example of an Indirect CoS
This indirect CoS uses the manager attribute of the target entry to identify the CoS template
entry, which varies depending on the different values of the attribute.
1. Add a new indirect CoS definition entry to the dc=example,dc=com suffix, using ldapmodify
as follows:
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. Add the indirect CoS definition to the dc=example,dc=com root suffix as follows:
dn: cn=indirectCoS,dc=example,dc=com
objectclass: top
objectclass: cosSuperDefinition
objectclass: cosIndirectDefinition
cosIndirectSpecifier: manager
cosAttribute: departmentNumber
If the directory or modify the manager entries already contain the departmentNumber attribute,
then no other attribute needs to be added to the manager entries. The definition entry looks in
the target suffix (the entries under dc=example,dc=com) for entries containing the manager
attribute because this attribute is specified in the cosIndirectSpecifier attribute of the
definition entry). It then checks the departmentNumber value in the manager entry that is listed.
The value of the departmentNumber attribute will automatically be relayed to all of the
manager's subordinates that have the manager attribute. The value of departmentNumber will
Managing CoS from the Command-Line
159