You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2018/06/11 11:58:00 UTC

[jira] [Created] (QPID-8208) [Broker-J] Improve unexpected exception handling for LDAP connections in SimpleLDAPAuthenticationProvider

Alex Rudyy created QPID-8208:
--------------------------------

             Summary: [Broker-J] Improve unexpected exception handling for LDAP connections in SimpleLDAPAuthenticationProvider
                 Key: QPID-8208
                 URL: https://issues.apache.org/jira/browse/QPID-8208
             Project: Qpid
          Issue Type: Bug
          Components: Broker-J
    Affects Versions: qpid-java-broker-7.0.4, qpid-java-broker-7.0.1, qpid-java-6.1.5, qpid-java-broker-7.0.0, qpid-java-6.1.4, qpid-java-6.0.8, qpid-java-6.1.3, qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-6.1.1, qpid-java-6.0.6, qpid-java-6.1, qpid-java-6.0.5, qpid-java-6.0.4, qpid-java-6.0.3, qpid-java-6.0.2, qpid-java-6.0.1, qpid-java-6.0, 0.32, qpid-java-broker-7.0.2, qpid-java-broker-7.0.3, qpid-java-6.1.6
            Reporter: Alex Rudyy


The establishment of connection with LDAP using  default {{com.sun.jndi.ldap.LdapCtxFactory}} can end-up in unexpected exception thrown from {{com.sun.jndi.ldap.LdapClient}}. Thought, it looks like a defect in {{LdapClient}}, the unexpected exceptions should be handled appropriately. The exception should be logged and the authentication failure error should be returned back to the client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org