You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Grzegorz Grzybek (JIRA)" <ji...@apache.org> on 2016/07/05 07:19:11 UTC

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

Grzegorz Grzybek created KARAF-4607:
---------------------------------------

             Summary: ldap connection pool not created when using ssl (ldaps)
                 Key: KARAF-4607
                 URL: https://issues.apache.org/jira/browse/KARAF-4607
             Project: Karaf
          Issue Type: Bug
          Components: karaf-jndi
    Affects Versions: 3.0.7, 4.0.5, 2.4.4
            Reporter: Grzegorz Grzybek


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)