Chapter 3. Configuring Directory Databases

server. Access controls are always evaluated on the remote server. For the user to modify or write data successfully to the remote server, set up the correct access controls on the remote server. For more information about how access controls are evaluated in the context of chained operations, see Section 3.5, “Database Links and Access Control Evaluation”.

3.3. Chaining Using SSL

Database links can be configured to communicate with the remote server using SSL. Using SSL to chain involves the following steps:

1.Enable SSL on the remote server.

2.Specify the LDAP URL of the remote server in SSL format in the nsFarmServerURL attribute. For more information about this attribute, see Section 3.2.2.3, “Providing an LDAP URL”. For example:

nsFarmServerURL: ldaps://africa.example.com:636/

3.Enable SSL on the server that contains the database link.

For more information on enabling SSL, see Section 1.1, “Enabling SSL: Summary of Steps”.

When the database link and remote server are configured to communicate using SSL, this does not mean that the client application making the operation request must also communicate using SSL. The client can bind using a normal port.

3.4. Maintaining Database Links

This section describe how to update and delete existing database links. It contains the following procedures:

Section 3.4.1, “Updating Remote Server Authentication Information”

Section 3.4.2, “Deleting Database Links”

3.4.1. Updating Remote Server Authentication Information

To update the bind DN and password used by the database link to connect to the remote server, do the following:

86

Page 106
Image 106
HP UX Red Hat Direry Server Software manual Chaining Using SSL, Maintaining Database Links