[KARAF-4607] ldap connection pool not created when using ssl (ldaps)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.4, 4.0.5, 3.0.7
• Fix Version/s: 4.1.0, 4.0.6, 3.0.8, 2.4.5
• Component/s: karaf
• Assignee: Guillaume Nodet
• Reporter: Grzegorz Grzybek
• Created: 05/Jul/16 07:18
• Updated: 19/Dec/19 17:30
• Resolved: 25/Jul/16 16:53

Description

When org.apache.karaf.jaas.modules.ldap.LDAPLoginModule is used with ldaps:// protocol and default (Sun) JNDI provider is used, LDAP connection pool is not used.

The problem is that com.sun.jndi.ldap.LdapPoolManager#isPoolingAllowed() does several checks when custom java.naming.ldap.factory.socket (which is the case with Karaf). Such factory has to implement java.util.Comparator interface, but actually String objects (com.sun.jndi.ldap.ClientId#socketFactory()) are passed to compare() method.

Issue Links

• relates to: KARAF-6517 LDAPLoginModule + SSL + connection timeout problem
• links to: GitHub Pull Request #206
• links to: GitHub Pull Request #207
• links to: GitHub Pull Request #208
• links to: GitHub Pull Request #209