Red Hat DIRECTORY SERVER 7.1, Administrator'S Manual

Page: 112 / 652

Creating and Maintaining Database Links
112 Red Hat Directory Server Administrator’s Guide • May 2005
• Providing an LDAP URL
• Providing a List of Failover Servers
• Summary of Cascading Chaining Configuration Attributes
• Database Link Configuration Example
Providing Suffix Information
Use the
nsslapd-suffix
attribute to define the suffix managed by your database
link. For example, if you want your database link to point to the people
information for a remote site of your company, you would enter the following
suffix information:
nsslapd-suffix: l=Zanzibar,ou=people,dc=example,dc=com
The suffix information is stored in the
cn=
database_link_name
,cn=chaining
database,cn=plugins,cn=config
entry.
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 45.
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 ACIs, refer to “Managing Access
Control,” on page 201.
2.
On the server containing the database like, you need to do the following:
NOTE After creation time, any alterations you make to the
nsslapd-suffix
attribute occur only after you have restarted the
server containing the database link.