Random connection handler picks same ldap server every time

[Daniel Fisher]

On Tue, Oct 8, 2013 at 5:10 AM, Joep Driesen <Joep.Driesen at kuleuven.be>wrote:

> Off course. Here is an ldap trace log of startup + 1 successful login
> attempt:
>
> 11:00:36.679 - TRACE
> [edu.vt.middleware.ldap.handler.DefaultConnectionHandler:93] -
> [TP-Processor1:] - setting connectionStrategy: RANDOM
> 11:00:36.682 - TRACE
> [edu.vt.middleware.ldap.auth.AuthenticatorConfig:1119] - [TP-Processor1:] -
> setting connectionHandler:
> edu.vt.middleware.ldap.handler.DefaultConnectionHandler at 27f899e9
> 11:00:36.687 - TRACE
> [edu.vt.middleware.ldap.auth.AuthenticatorConfig:1276] - [TP-Processor1:] -
> setting bindDn: cn=idp,ou=admins,dc=example,dc=com
> 11:00:36.688 - TRACE [edu.vt.middleware.ldap.auth.AuthenticatorConfig:290]
> - [TP-Processor1:] - setting userFilter: uid={0}
> 11:00:36.689 - TRACE
> [edu.vt.middleware.ldap.auth.AuthenticatorConfig:1309] - [TP-Processor1:] -
> setting bindCredential: <suppressed>
> 11:00:36.693 - TRACE
> [edu.vt.middleware.ldap.auth.AuthenticatorConfig:1119] - [TP-Processor1:] -
> setting connectionHandler:
> edu.vt.middleware.ldap.handler.DefaultConnectionHandler at 3240a47f
>

The connectionHandler is getting set twice and overwriting the one you want.
Remove the tls="false" option, as that is the default and that option is
mutually exclusive with connectionHandler="..."

If in the future you want to use startTLS instead of SSL with the random
connection strategy, you simply need to set a different connection handler:
connectionHandler="edu.vt.middleware.ldap.handler.TlsConnectionHandler{{
connectionStrategy=RANDOM}}"

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131008/d95b53da/attachment.html