Creating and Maintaining Database Links
Chapter 3
Configuring Directory Databases
141
Add the local proxy authorization ACI to the
c=africa,ou=people,dc=example,dc=com
entry:
aci:(targetattr="*")(target="l=Zanzibar,c=africa,ou=people,
dc=example,dc=com")(version 3.0; acl "Proxied authorization for
database links"; allow (proxy) userdn = "ldap:///cn=server1
proxy admin,cn=config";)
Then add the local client ACI that will allow the client operation to succeed on
Server 2, given that ACI checking is turned on. This ACI is the same as the ACI you
will create on the destination server to provide access to the
l=Zanzibar,c=africa,ou=people,dc=example,dc=com
branch. You may decide
that you want all users within
c=us,ou=people,dc=example,dc=com
to have
update access to the entries in
l=Zanzibar,c=africa,ou=people,dc=example,dc=com
on server three. The
following ACI is the ACI you would need to create on the
c=africa,ou=people,dc=example,dc=com
suffix on Server 2 to allow this:
aci:(targetattr="*")(target="l=Zanzibar,c=africa,ou=people,
dc=example,dc=com")(version 3.0; acl "Client authorization for
database links"; allow (all) userdn =
"ldap:///uid=*,c=us,ou=people,dc=example,dc=com";)
This ACI allows clients that have a
uid
in
c=us,ou=people,dc=example,dc=com
on Server 1 to perform any type of operation on the
l=Zanzibar,c=africa,ou=people,dc=example,dc=com
suffix tree on server
three. Should you have users on Server 2 under a different suffix that will require
additional rights on server three, you may need to add additional client ACIs on
Server 2.
Configuring Server Three
The final configuration step in our cascading chaining example is to configure
server three. First, you create an administrative user on server three for Server 2 to
use for proxy authorization:
NOTE
To create these ACIs, it is assumed that the database corresponding
to the
c=africa,ou=people,dc=example,dc=com
suffix already
exists to hold the entry. This database needs to be associated with a
suffix above the suffix specified in the
nsslapd-suffix
attribute of
each database link. That is, the suffix on the final destination server
should be a sub suffix of the suffix specified on the intermediate
server.
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 ...