[jboss-jira] [JBoss JIRA] (WFLY-2214) Allow existing environment properties to be set for outbound LDAP connections used by security realms.

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse updated WFLY-2214:
-----------------------------------

    Summary: Allow existing environment properties to be set for outbound LDAP connections used by security realms.  (was: LDAP security realm needs to have configurable timeouts)

    
> Allow existing environment properties to be set for outbound LDAP connections used by security realms.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-2214
>                 URL: https://issues.jboss.org/browse/WFLY-2214
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.0.0.Alpha4
>            Reporter: Derek Horton
>            Assignee: Darran Lofthouse
>             Fix For: 8.0.0.CR1
>
>
> LDAP security realm needs to have configurable timeouts.
> The default LDAP connection timeout appears to be 2 minutes.  If the ldap server is down, it could take 2 minutes for the connection to timeout.  This can cause unneeded delay if you have configured multiple ldap servers for  failover / redundancy.
> The following hack appears to work:
> +++ domain-management/src/main/java/org/jboss/as/domain/management/connections/ldap/LdapConnectionManagerService.java
> @@ -132,6 +132,7 @@ public class LdapConnectionManagerService implements Service<LdapConnectionManag
>          result.put(Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
>          String url = config.require(URL).asString();
>          result.put(Context.PROVIDER_URL,url);
> +        result.put("com.sun.jndi.ldap.connect.timeout", "500");
>          return result;
>      }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira