HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

Figure 9 Sample classic CoS
In this example, the CoS definition entry's cosSpecifier attribute specifies the employeeType
attribute. This attribute, in combination with the template DN, identify the template entry as
cn=sales,cn=exampleUS,cn=data. The template entry then provides the value of the
postalCode attribute to the target entry.
5.2.1.6 Searches for CoS-specified attributes
CoS definitions provide values for attributes in entries. For example, a CoS can set the postalCode
attribute for every entry in a subtree. Searches against those CoS-defined attributes, however, do
not behave like searches against regular entries.
• If the CoS-defined attribute is indexed with any kind of index (including presence), then any
attribute with a value set by the CoS is not returned with a search. For example:
◦ The postalCode attribute for Ted Morris is defined by a CoS.
◦ The postalCode attribute for Barbara Jensen is set in her entry.
◦ The postalCode attribute is indexed.
If an ldapsearch command uses the filter (postalCode=*), then Barbara Jensen's entry
is returned, while Ted Morris's is not.
• If the CoS-defined attribute is not indexed, then every matching entry is returned in a search,
regardless of whether the attribute value is set locally or with CoS. For example:
◦ The postalCode attribute for Ted Morris is defined by a CoS.
◦ The postalCode attribute for Barbara Jensen is set in her entry.
◦ The postalCode attribute is not indexed.
If an ldapsearch command uses the filter (postalCode=*), then both Barbara Jensen's
and Ted Morris's entries are returned.
• CoS allows for an override, an identifier given to the cosAttributeattribute in the CoS
entry, which means that local values for an attribute can override the CoS value. If an override
is set on the CoS, then an ldapsearch operation will return a value for an entry even if the
5.2 Assigning class of service 191