Access Control And Cos - Netscape DIRECTORY SERVER 6.01 - ADMINISTRATOR Administrator's Manual

Assigning Class of Service
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: LDAPsubentry
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
override
the target entry.
The corresponding CoS template entry looks as follows:
dn:cn="cn=ManagerRole,ou=people,dc=example,dc=com",cn=managerCOS,
dc=example,dc=com
objectclass: top
objectclass: LDAPsubentry
objectclass: extensibleobject
objectlass: cosTemplate
mailboxquota: 1000000
The template provides the value for the
NOTE

Access Control and CoS

The server controls access to attributes generated by a CoS in exactly the same way
as regular stored attributes. However, access control rules depending upon the
value of attributes generated by CoS will not work.
186 Netscape Directory Server Administrator's Guide • January 2002
attribute provides a value that, in combination with the
cosSpecifier
tells the CoS to override any existing
The role entry and the CoS definition and template entries should
be located at the same level in the directory tree.
attribute (in the example, the
attribute. An additional qualifier of
mailboxquota
mailboxquota
mailboxquota
nsRole
attributes values in
attribute, 1000000.