Red Hat Directory Server 8.0 Administrator's Guide

be added to any other search filter using OR (|):
ldapsearch -s sub -b ou=People,dc=example,dc=com
“(|(objectclass=*)(objectclass=ldapSubEntry))”
This search returns all regular entries in addition to CoS definition entries in the
ou=People,dc=example,dc=com subtree.
NOTE
The Console automatically shows CoS entries.
2.3.2. Creating the CoS Template Entry from the Command-Line
Each template entry is an instance of the cosTemplate object class.
NOTE
Consider adding the LDAPsubentry object class to a new template entry. Making
the CoS template entry an instance of the LDAPsubentry object classes allows
ordinary searches to be performed unhindered by the configuration entries.
However, if the template entry already exists and is used for something else,
such as a user entry, the LDAPsubentry object class does not need to be added
to the template entry.
The CoS template entry also contains the attribute generated by the CoS (as specified in the
cosAttribute attribute of the CoS definition entry) and the value for that attribute.
For example, a CoS template entry that provides a value for the postalCode attribute follows:
dn:cn=exampleUS,ou=data,dc=example,dc=com
objectclass: top
objectclass: extensibleObject
objectclass: cosTemplate
postalCode: 44438
It is possible to create CoS templates that compete with each other to provide an attribute
value. For example, there can be a multi-valued cosSpecifier attribute in the CoS definition
entry. Specifying the template priority on each template entry determines which template
provides the attribute value. Set the template priority using the cosPriority attribute. This
attribute represents the global priority of a particular template. A priority of zero is the highest
priority.
Managing CoS from the Command-Line
157