Advanced Feature: Configuring Cascading Chaining
87
Both ACIs will be placed on the database that contains the
c=africa,ou=people,dc=example,dc=com
suffix.
NOTE
To create these ACIs, the database corresponding to the
c=africa,ou=people,dc=example,dc=com
suffix must already exist 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.
a. 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";)
b. 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 created on the destination server to provide access to the
l=Zanzibar,c=africa,ou=people,dc=example,dc=com
branch. All users within
c=us,ou=people,dc=example,dc=com
may need to have update access to the entries in
l=Zanzibar,c=africa,ou=people,dc=example,dc=com
on server three. Create the
following ACI on Server 2 on the
c=africa,ou=people,dc=example,dc=com
suffix 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. If
there are users on Server 2 under a different suffix that will require additional rights on server
three, it may be necessary to add additional client ACIs on Server 2.
3.3.7.7.3. Configuring Server Three
1. Create an administrative user on server three for Server 2 to use for proxy authorization:
dn: cn=server2 proxy admin,cn=config
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
cn: server2 proxy admin
sn: server2 proxy admin
userPassword: secret
description: Entry for use by database links
Содержание DIRECTORY SERVER 8.0
Страница 18: ...xviii ...
Страница 29: ...Configuring the Directory Manager 11 6 Enter the new password and confirm it 7 Click Save ...
Страница 30: ...12 ...
Страница 112: ...94 ...
Страница 128: ...110 ...
Страница 190: ...Chapter 6 Managing Access Control 172 4 Click New to open the Access Control Editor ...
Страница 224: ...206 ...
Страница 324: ...306 ...
Страница 334: ...316 ...
Страница 358: ...340 ...
Страница 410: ...392 ...
Страница 420: ...402 ...
Страница 444: ...426 ...
Страница 454: ...436 ...
Страница 464: ...446 ...
Страница 484: ...466 ...
Страница 512: ...494 ...
Страница 522: ...504 ...