You can configure Content Server to use other LDAP directory servers for user authentication in the event that the first LDAP directory server is down. By default, the primary LDAP server handles all user authentication requests. However, if Content Server fails to bind to the primary LDAP directory server, you can define a way for it to bind to secondary LDAP servers, authenticate users, and then reattempt the connection with the primary LDAP directory server.
Enter the information for the secondary LDAP server, as described in Table 2.24.
Table 2.24. Secondary LDAP Server page properties
| Field | Description |
|---|---|
Name | Enter the name of the secondary LDAP server. |
| Hostname / IP Address | Type the name of the host on which the secondary LDAP directory server is running. |
Port | The port information is copied from the primary LDAP server. |
Binding Name | The binding name is copied from the primary LDAP server. |
Binding Password | Type the binding distinguished password used to authenticate requests to the secondary LDAP directory server by Content Server or the check password program. |
Confirm Password | Re-enter the binding password for verification. |
Bind to User DN | The bind to user DN information is copied from the primary LDAP server. |
Use SSL | The SSL information is copied from the primary LDAP server. |
SSL Port | The SSL port number is copied from the primary LDAP server. |
Certificate Location | The certificate location is copied from the primary LDAP server. |