Red Hat DIRECTORY SERVER 8.0, Administration Manual

Page: 83 / 552

Creating a New Database Link
65
NOTE
After creating the database link, any alterations to the
nsslapd-nsslapd-suffix
attribute are applied only after the server containing the database link is restarted.
3.3.2.2.2. Providing Bind Credentials
For a request from a client application to be chained to a remote server, special bind credentials can
be supplied for the client application. This gives the remote server the proxied authorization rights
needed to chain operations. Without bind credentials, the database link binds to the remote server as
anonymous
.
Providing bind credentials involves the following steps:
1. On the remote server, do the following:
• Create an administrative user for the database link.
For information on adding entries, see
Chapter 2, Creating Directory Entries
.
• Provide proxy access rights for the administrative user created in step 1 on the subtree chained
to by the database link.
For more information on configuring ACIs, see
Chapter 6, Managing Access Control
2. On the server containing the database link, use
ldapmodify
to provide a user DN for the
database link in the
nsMultiplexorBindDN
attribute of the
cn=
database_link,
cn=chaining
database,cn=plugins,cn=config
entry.
WARNING
The
nsMultiplexorBindDN
cannot be that of the Directory Manager.
Use
ldapmodify
to provide a user password for the database link in the
nsMultiplexorCredentials
attribute of the
cn=
database_link,
cn=chaining
database,cn=plugins,cn=config
entry.
For example, a client application sends a request to Server A. Server A contains a database link that
chains the request to a database on Server B.