Netscape DIRECTORY SERVER 6.1 - ADMINISTRATOR Administrator's Manual page 108

Creating and Maintaining Database Links
For more information on ACIs, refer to "Managing Access Control," on page 193.
For more information about the proxy authentication control, refer to the C-SDK
documentation at
NOTE
Providing an LDAP URL
On the server containing your database link, you have to identify the remote server
that the database link connects with using an LDAP URL. Unlike the standard
LDAP URL format, the URL of the remote server does not specify a suffix. It takes
the following form:
ldap://
You specify the URL of the remote server using the
the
cn=
of the configuration file. For example, the
follows:
nsFarmServerURL: ldap://example.com:389/
Do not forget to use the trailing slash (/) at the end of the URL.
If you want to the database link to connect to the remote server using LDAP over
SSL, the LDAP URL of the remote server takes the following form:
ldaps://
For more information about chaining and SSL, refer to "Chaining Using SSL," on
page 113.
Providing a List of Failover Servers
You can include additional LDAP URLs for servers to use in the case of failure. To
do so, add alternate servers to the
For example, you might enter the following:
nsFarmServerURL: ldap://example.com us.example.com:389
africa.example.com:1000/
108 Netscape Directory Server Administrator's Guide • August 2002
http://enterprise.netscape.com/docs
When a database link is used by a client application to create or
modify entries, the attributes
do not reflect the real creator or modifier of the entries. These
attributes contain the name of the administrative user granted
proxied authorization rights on the remote data server.
servername portnumber
:
database_link_name
,cn=chaining database,cn=plugins,cn=config
servername portnumber
:
creatorsName
/
nsFarmServerURL
nsFarmServerURL
/
nsFarmServerURL
.
and
modifiersName
attribute in
might appear as
attribute, separated by spaces.
entry