Table of Contents
Advertisement
Creating and Maintaining Database Links
Configuring Server Two
Next, you create a proxy administrative user on server two. This administrative
user will be used to allow server one to bind and authenticate to server two. Bear in
mind that it is useful to choose a proxy administrative user name which is specific
to server one as it is the proxy administrative user which will allow server one to
bind to server two. You create the proxy administrative user as follows:
dn: cn=server1 proxy admin,cn=config
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
cn: server1 proxy admin
sn: server1 proxy admin
userPassword: secret
description: Entry for use by database links
CAUTION
Next, you configure the database link, DBLink2, on server two. Using
specify the configuration information for DBLink2 as follows:
dn: cn=DBLink2,cn=chaining database,cn=plugins,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsBackendInstance
nsslapd-suffix: l=Zanzibar,c=africa,ou=people,dc=example,dc=com
nsfarmserverurl: ldap://zanz.africa.example.com:389/
nsmultiplexorbinddn: cn=server2 proxy admin,cn=config
nsmultiplexorcredentials: secret
cn: DBLink2
nsCheckLocalACI:on
dn: cn="l=Zanzibar,c=africa,ou=people,dc=example,dc=com",cn=mapping
tree,cn=config
objectclass: top
objectclass: extensibleObject
objectclass: nsMappingTree
nsslapd-state: backend
nsslapd-backend: DBLink2
nsslapd-parent-suffix:"c=africa,ou=people,dc=example,dc=com"
cn: l=Zanzibar,c=africa,ou=people,dc=example,dc=com
126
Netscape Directory Server Administrator's Guide • January 2002
Do not use the Directory Manager or Administrator ID user as the
proxy administrative user on the remote server. This creates a
security hole.
,
ldapmodify
Advertisement
Table of Contents
