The change to enforce hostname verification for all LDAPS connections broke
non-default connection strategies.
The same JNDI environment is provided after a connection failure and since that
environment has a SocketFactory associated with it, a new hostname verifier is
not configured.
This causes hostname verification failures on all subsequent connections.
See https://issues.shibboleth.net/jira/browse/SIDP-542
Original issue reported on code.google.com by dfis...@gmail.com on 22 May 2012 at 3:57
Original issue reported on code.google.com by
dfis...@gmail.com
on 22 May 2012 at 3:57