Red Hat DIRECTORY SERVER 8.0, Руководство администратора

Страница: 145 / 552

Managing CoS Using the Console
127
• Select
Overrides target entry attribute and is operational
to make the attribute override the
local value and to make the attribute operational, so that it is not visible to client applications
unless explicitly requested.
• Select
Does not override target entry attribute and is operational
to tell the directory to
return a generated value only if there is no corresponding attribute value stored with the entry
and to make the attribute operational (so that it is not visible to client applications unless
explicitly requested).
NOTE
An attribute can only be made operational if it is also defined as operational in the
schema. For example, if a CoS generates a value for the
description
attribute,
you cannot select
Overrides target entry attribute and is operational
because this
attribute is not marked operational in the schema.
7. Click
Template
in the left pane. In the right pane, select how the template entry is identified.
•
By its DN.
To have the template entry identified by only its DN (a pointer CoS), enter the DN of
the template in the
Template DN
field. Click
Browse
to locate the DN on the local server. This
will be an exact DN, such as
cn=CoS template,ou=People,dc=example,dc=com
.
•
Using the value of one of the target entry's attribute.
To have the template entry identified by
the value of one of the target entry's attributes (an indirect CoS), enter the attribute name in
the
Attribute Name
field. Click
Change
to select a different attribute from the list of available
attributes.
•
Using both its DN and the value of one of the target entry's attributes.
To have the template
entry identified by both its DN and the value of one of the target entry's attributes (a classic
CoS), enter both a template DN and an attribute name. The template DN in a classic CoS is
more general than for a pointer CoS; it references the suffix or sub suffix where the template
entries will be (there can be more than one template).
8. Click
OK
.
5.2.2.2. Creating the CoS Template Entry
For a pointer CoS or a classic CoS, there must be a template entry, according to the template DN set
when the class of service was created. Although the template entries can be placed anywhere in the
directory as long as the
cosTemplateDn
attribute reflects that DN, it is best to place the template
entries under the CoS itself.
For a pointer CoS, make sure that this entry reflects the exact DN given when the CoS was created.
For a classic CoS, the template DN should be recursive, pointing back to the CoS entry itself as the
base suffix for the template.
1. In the Directory Server Console, select the
Directory
tab.
2. Browse the tree in the left navigation pane, and select the parent entry that contains the class of
service.
The CoS appears in the right pane with other entries.