IdPv3 - authn ldap - connection strategy?

John Horne john.horne at plymouth.ac.uk
Thu Mar 24 12:11:22 EDT 2016


On Thu, 2016-03-24 at 10:10 -0400, Craig Pluchinsky wrote:
> I modified the Authentication handler section in 
> authn/ldap-authn-config.xml to add connectionStrategy for default 
> provider (JNDI).  Note I did remove connection pooling and switched
> to 
> BindAuthenticationHandler.  This worked but might not the correct
> way.
> 
>      <bean id="authHandler" 
> class="org.ldaptive.auth.BindAuthenticationHandler" 
> p:connectionFactory-ref="bindConnectionFactory" />
>      <bean id="bindConnectionFactory" 
> class="org.ldaptive.DefaultConnectionFactory" 
> p:connectionConfig-ref="bindConnectionConfig" 
> p:provider-ref="jndiProvider"/>
>      <bean id="jndiProvider" 
> class="org.ldaptive.provider.jndi.JndiProvider" 
> p:providerConfig-ref="jndiConfig" />
>      <bean id="jndiConfig" 
> class="org.ldaptive.provider.jndi.JndiProviderConfig" 
> p:connectionStrategy="RANDOM" />
>      <bean id="bindConnectionConfig" parent="connectionConfig" />
> 
Thanks for that. I would have thought though that the strategy would
have been part of the 'connectionConfig', since that is where the URLs
are defined, rather than a per-provider thing.

I have no problem with using a pool, but would like it to use round-
robin when selecting which LDAP server/URL should be used for any new
connections.




John.
 
-- 
John Horne                   Tel: +44 (0)1752 587287
Plymouth University, UK




More information about the users mailing list