Netscape NETSCAPE DIRECTORY SERVER 6.02, Administrator'S Manual

Page: 102 / 568

Creating and Maintaining Database Links
102 Netscape Directory Server Administrator’s Guide • May 2002
Providing Bind Credentials
For a request from a client application to be chained to a remote server, you can
provide special bind credentials for the client application. This gives the remote
server the proxied authorization rights needed to chain operations. If you do not
specify bind credentials, the database link binds to the remote server as
anonymous.
Providing bind credentials involves the following steps:
1.
On the remote server, you need to do the following:
a.
Create an administrative user for the database link.
For information on adding entries, see “Creating Directory Entries,” on
page 41.
b.
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 ACI’s, refer to “Managing Access
Control,” on page 189.
2.
On the server containing the database like, you need to do the following:
a.
Use
ldapmodify
to provide a user DN for the database link in the
nsMultiplexorBindDN
attribute of the
cn=
database_link_name
,cn=chaining database,cn=plugins,cn=config
entry.
b.
Use
ldapmodify
to provide a user password for the database link in the
nsMultiplexorCredentials
attribute of the
cn=
database_link_name
,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.
CAUTION The
nsMultiplexorBindDN
cannot be that of the Directory
Manager.