Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Configure LDAP user registries

Configure multiple LDAP servers for user registry failover

WAS security can be configured to attempt failovers between multiple Lightweight Directory Access Protocol (LDAP) hosts. The multiple LDAP servers involved in the failover can be replicas that are replicated from the same master LDAP server, or they can be any LDAP host with the same schema. That is any LDAP host that contains data that is imported from the same LDAP data interchange format (LDIF) file.

When WAS attempts failovers between multiple LDAP hosts, system properties are exchanged. WAS v6.1.0 manages the SSL configuration and these system properties. We cannot expect to set system properties yourself and expect the failover to succeed.

Procedure

1. Start the dmgr process.

   1. Start the Command Prompt application.
   2. Change directories to $PROFILE_ROOT/bin.

   3. Enter startManager.

2. Start the wsadmin Command Prompt application.

   1. Start the Command Prompt application.
   2. Change directories to $PROFILE_ROOT/bin.

   3. Enter the following command:

      wsadmin –user username –password password 

3. Configure a second LDAP server for failover.

   1. Enter the following command to set the failover LDAP server hostname:

      set ldapServer [ldap server hostname]
      

   2. Enter the following command to set the LDAP server port number:

      set ldapPort [ldap server port]
      

   3. Enter the following command to set the WebSphere LDAP failover variable:

      set Attrs2 [list [list hosts [list [list [list host $ldapServer] [list port $ldapPort]]]]]
      

   4. Modify the LDAP configuration to add the failover LDAP server by entering the following command:

      set result [$AdminConfig list LDAPUserRegistry]
      

   5. Find the LDAP server configID by entering the following command:

      $AdminConfig modify $result $Attrs2
      

   6. Enter the following command to save the configuration change:

      $AdminConfig save 

   7. Enter exit to quit the Command Prompt application. The following is an example of the Command Prompt application output:

      wsadmin>set ldapServer [list xxxx.xxxx.xxx.com]
      xxxx.xxxx.xxx.com
      wsadmin>set ldapPort [list NNN]
      NNN
      wsadmin>set Attrs2 [list [list hosts [list [list [list host $ldapServer] [list port $ldapPort]]]]]
      {hosts {{{host xxxx.xxxx.xxx.com} {port NNN}}}}
      wsadmin> set result [$AdminConfig list LDAPUserRegistry]
      (cells/Father2Cell01|security.xml#LDAPUserRegistry_1)
      wsadmin>$AdminConfig modify $result $Attrs2
      
      wsadmin>$AdminConfig save
      

4. Review the configuration change by opening the security.xml file with a text editor and review the new entry.
5. Stop the dmgr.

   1. Start the Command Prompt application.
   2. Change directories to $PROFILE_ROOT/bin.

   3. To stop the dmgr, run:

      stopManager –user username –password password 

Test an LDAP server for user registry failover
Delete LDAP endpoints using wsadmin
Configure LDAP user registries

+

Search Tips   |   Advanced Search