Assigning Class of ServiceChapter 5 Advanced Entry Management 177• Managing CoS Using the Console• Managing CoS From the Command Line• Creating Role-Based Attributes• Access Control and CoSAbout CoSClients of the Directory Server read the attributes on a user’s entry. With CoS, someattribute values may not be stored with the entry itself. Instead, they are generatedby 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 youare using. Like the role definition entry, it inherits from the LDAPsubentryobject class. The CoS definition entry is below the branch at which it iseffective.• Template Entry—The CoS template entry contains a list of the shared attributevalues. Changes to the template entry attribute values are automaticallyapplied to all the entries within the scope of the CoS. A single CoS might havemore than one template entry associated with it.The CoS definition entry and template entry interact to provide attributeinformation to their target entries, any entry within the scope of the CoS.The following sections describe the entries that make up a CoS in more detail andprovide examples of each type of CoS.About the CoS Definition EntryThe CoS definition entry is an instance of the cosSuperDefinition object class.The CoS definition entry also contains an object class that specifies the type oftemplate entry it uses to generate the entry. You can specify three different objectclasses depending upon the type of CoS you want to use. The target entries sharethe same parent as the CoS definition entry.NOTE LDAP search requests containing a filter that references an attributedefined by a CoS may return unexpected results. Take care whendeciding which attributes to generate using a CoS.
