Table of Contents
Advertisement
•
Managing CoS Using the Console
•
Managing CoS From the Command Line
•
Creating Role-Based Attributes
•
Access Control and CoS
About CoS
Clients of the Directory Server read the attributes on a user's entry. With CoS, some
attribute values may not be stored with the entry itself. Instead, they are generated
by class of service logic as the entry is sent to the client application.
Each CoS is comprised of the following two types of entry in your directory:
•
CoS Definition Entry—The CoS definition entry identifies the type of CoS you
are using. Like the role definition entry, it inherits from the
object class. The CoS definition entry is below the branch at which it is
effective.
•
Template Entry—The CoS template entry contains a list of the shared attribute
values. Changes to the template entry attribute values are automatically
applied to all the entries within the scope of the CoS. A single CoS might have
more than one template entry associated with it.
The CoS definition entry and template entry interact to provide attribute
information to their target entries, any entry within the scope of the CoS.
LDAP search requests containing a filter that references an attribute
NOTE
defined by a CoS may return unexpected results. Take care when
deciding which attributes to generate using a CoS.
The following sections describe the entries that make up a CoS in more detail and
provide examples of each type of CoS.
About the CoS Definition Entry
The CoS definition entry is an instance of the
The CoS definition entry also contains an object class that specifies the type of
template entry it uses to generate the entry. You can specify three different object
classes depending upon the type of CoS you want to use. The target entries share
the same parent as the CoS definition entry.
Assigning Class of Service
LDAPsubentry
cosSuperDefinition
Chapter 5
Advanced Entry Management
object class.
177
Advertisement
Table of Contents
Troubleshooting
