You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/09 14:35:20 UTC

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

    [ https://issues.apache.org/jira/browse/KARAF-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413622#comment-15413622 ] 

ASF GitHub Bot commented on KARAF-4607:
---------------------------------------

Github user grgrzybek closed the pull request at:

    https://github.com/apache/karaf/pull/209


> 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: 2.4.4, 4.0.5, 3.0.7
>            Reporter: Grzegorz Grzybek
>            Assignee: Guillaume Nodet
>             Fix For: 4.1.0, 4.0.6, 3.0.8, 2.4.5
>
>
> 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)