Creating Role-Based Attributes - Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual

Assigning Class of Service

Creating Role-Based Attributes

You can create classic CoS schemes that generate attribute values for an entry
based on the role possessed by the entry. For example, you could use role-based
attributes to set the server look through limit on an entry-by-entry basis.
To create a role-based attribute, use the
the CoS definition entry of a classic CoS. Because the
multi-valued, you can define CoS schemes that have more than one possible
template entry. To resolve the ambiguity of which template entry to use, you can
include the
For example, you can create a CoS that allows members of the manager role to
exceed the standard mailbox quota. The manager role exists as follows:
dn: cn=ManagerRole,ou=people,dc=example,dc=com
objectclass: top
objectclass: nsRoleDefinition
objectclass: nsComplexRoleDefinition
objectclass: nsFilteredRoleDefinition
cn: ManagerRole
nsRoleFilter: o=managers
Description: filtered role for managers
The classic CoS definition entry would look as follows:
dn: cn=managerCOS,dc=example,dc=com
objectclass: top
objectclass: cosSuperDefinition
objectlass: cosClassicDefinition
cosTemplateDn: cn=managerCOS,dc=example,dc=com
cosSpecifier: nsRole
cosAttribute: mailboxquota override
The
cosTemplateDn
attribute specified in the
attribute of the target entry), identifies the CoS template entry. The CoS template
entry provides the value for the
of
override
in the target entry.
The corresponding CoS template entry looks as follows:
198 Red Hat Directory Server Administrator's Guide • May 2005
attribute in your CoS template entry.
cosPriority
attribute provides a value that, in combination with the
cosSpecifier
mailboxquota
tells the CoS to override any existing
attribute as the
nsRole
nsRole
attribute (in the example, the
attribute. An additional qualifier
mailboxquota
in
cosSpecifier
attribute can be
nsRole
attributes values