B.0 Using LDAP Server Load Balancing and Failover

You can add multiple LDAP servers to an authentication profile and to an access control pool:

iChainĀ® 2.3 SP4 IR3 has modified the code that performs such tasks as monitoring the health of each LDAP server and re-enabling servers that have come online. All pools now use the same algorithms for these tasks. For load balancing, they use a modified round robin algorithm. The next server in the list is used for the next request unless the request is an authentication request. When a user requests authentication, the initial request derives persistence from the username. This allows the user to use the same LDAP server for subsequent requests. This solves a problem with Form Fill when deleteRemembered is enabled. The user returns to the same server where the secrets have been deleted rather than being sent to the next LDAP server in the list, which might not have been synchronized with the LDAP server that deleted the outdated secrets.

The following screens allow you to monitor the health of your LDAP configuration: