p:responseTimeout not present in LDAP connections

[Youssef GHORBAL]

That’s exactly what I did !

Youssef
---------------
> On 26 Apr 2016, at 16:53, Jeremy A Scott <jeremy.scott at wisc.edu> wrote:
> 
> For my deployments, I have to integrate with directory servers that are not local and sometimes things get weird, backhoe etc...
> 
> I added an additional property to idp.properties called 'idp.authn.LDAP.responseTimeout' and represented it here in authn/ldap-authn-config.xml:
> 
>    <!-- Connection Configuration -->
>    <bean id="connectionConfig" class="org.ldaptive.ConnectionConfig" abstract="true" p:ldapUrl="%{idp.authn.LDAP.ldapURL}"
>        p:useStartTLS="%{idp.authn.LDAP.useStartTLS:true}"
>        p:useSSL="%{idp.authn.LDAP.useSSL:false}"
>        p:connectTimeout="%{idp.authn.LDAP.connectTimeout:3000}"
>        p:responseTimeout="%{idp.authn.LDAP.responseTimeout:3000}"
>        p:sslConfig-ref="sslConfig" />
> 
> I also added 'idp.attribute.resolver.LDAP.responseTimeout' which I use in a separate bean resource configuration file for the attribute resolver. 
> 
> Hope this helps.
> 
> -Jeremy
> 
>> On Apr 22, 2016, at 4:43 PM, Cantor, Scott <cantor.2 at OSU.EDU> wrote:
>> 
>>> On 22 Apr 2016, at 22:48, Cantor, Scott <cantor.2 at osu.edu> wrote:
>>> 
>>>> That file is not a system configuration file, I would assume that any non-
>>> trivial deployer would need to edit it.
>>> 
>>> Fair enough !
>>> I'm still not so java/spring fluent though :)
>> 
>> I think it needs work to be usable. I was just pointing out that regardless of what's in it, it's not a protected file.
>> 
>> -- Scott
>> 
>> -- 
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net