Red Hat Directory Server 8.0 Administrator's Guide

• Classic CoS. A classic CoS identifies the template entry using a combination of the template
entry's base DN and the value of one of the target entry's attributes.
For more information about the object classes and attributes associated with each type of CoS,
refer to Section 2.3, “Managing CoS from the Command-Line”.
If the CoS logic detects that an entry contains an attribute for which the CoS is generating
values, the CoS, by default,supplies the client application with the attribute value in the entry
itself. However, the CoS definition entry can control this behavior.
2.1.2. About the CoS Template Entry
The CoS template entry contains the value or values of the attributes generated by the CoS
logic. The CoS template entry contains a general object class of cosTemplate. The CoS
template entries for a given CoS are stored in the directory tree along with the CoS definition.
The relative distinguished name (RDN) of the template entry is determined by one of the
following:
• The DN of the template entry alone.
This type of template is associated with a pointer CoS definition.
• The value of one of the target entry's attributes.
The attribute used to provide the relative DN to the template entry is specified in the CoS
definition entry using the cosIndirectSpecifier attribute. This type of template is
associated with an indirect CoS definition.
• By a combination of the DN of the subtree where the CoS performs a one level search for
templates and the value of one of the target entry's attributes.
This type of template is associated with a classic CoS definition.
2.1.3. How a Pointer CoS Works
An administrator creates a pointer CoS that shares a common postal code with all of the entries
stored under dc=example,dc=com. The three entries for this CoS appear as illustrated in
Figure 5.1, “Sample Pointer CoS”.
About CoS
145