Random connection handler picks same ldap server every time
Joep Driesen
Joep.Driesen at kuleuven.be
Mon Oct 7 02:41:19 EDT 2013
Hi all,
I am trying to setup an Active-Active configuration using a jaas login.conf file. Currently my setup is as follows:
ShibUserPassAuth {
edu.vt.middleware.ldap.jaas.LdapLoginModule required
ldapUrl="ldaps://ldap1.example.com:636 ldaps://ldap2.example.com:636"
ssl="true"
connectionHandler="edu.vt.middleware.ldap.handler.DefaultConnectionHandler{{connectionStrategy=RANDOM}}"
timeout="1000"
baseDn="---"
bindDn="---"
bindCredential="---"
tls="false"
userFilter="uid={0}"
setLdapPrincipal="false"
subtreeSearch="true"
;
};
It seems shibboleth always picks the first LDAP server for authentication, whereas I would like it to switch between both servers. I'm not sure how to troubleshoot this, so any advice would be welcome.
I have made sure that both LDAP servers work correctly when used on their own, so that should not be the problem...
Regards,
Joep
More information about the users
mailing list