Bind Rules
Chapter 6
Managing Access Control
229
The bind rule is evaluated to be true if the bind DN belongs to the role specified in
the
exampleEmployeeReportsTo
attribute of the targeted entry. For example, if
you create a nested role for all managers in your company, you can use this
mechanism to grant managers at all levels access to information about employees
that are at a lower grade than themselves.
The DN of the role can be under any suffix in the database. If, in addition, you are
using filtered roles, the evaluation of this type of ACI uses a lot of resources on the
server.
If you are using a static role definition and the role entry is under the same suffix as
the targeted entry, you can use the following expression:
userattr = "ldap:///dc=example,dc=com?employeeReportsTo#ROLEDN"
In this example, the role entry is under the
dc=example,dc=com
suffix. The server
can process this type of syntax more quickly than the previous example.
Example with LDAPURL Bind Type
The following is an example of the
userattr
keyword associated with a bind
based on an LDAP filter:
userattr
=
"
myfilter
#
LDAPURL
"
The bind rule is evaluated to be true if the bind DN matches the filter specified in
the
myfilter
attribute of the targeted entry. The
myfilter
attribute can be replaced by
any attribute that contains an LDAP filter.
Example with Any Attribute Value
The following is an example of the
userattr
keyword associated with a bind
based on any attribute value:
userattr = "favoriteDrink#Beer"
The bind rule is evaluated to be true if the bind DN and the target DN include the
favoriteDrink
attribute with a value of
Beer
.
NOTE
This example assumes that you have added the
exampleEmployeeReportsTo
attribute to the schema and that all
employee entries contain this attribute. It also assumes that the
value of this attribute is the DN of a role entry.
For information on designing your schema, refer to
Red Hat
Directory Server Deployment Guide
. For information on adding
attributes to the schema, see “Creating Attributes,” on page 377.
Summary of Contents for DIRECTORY SERVER 7.1
Page 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Page 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Page 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...