activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMQ-6148) When use LDAP auth, Activemq should not always connect to ldap service to do authentication
Date Tue, 09 Feb 2016 12:25:18 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully reopened AMQ-6148:
-----------------------------

looks like we could pull back the fix from artemis for this. I don't see any reason why we
cannot cache the ldap context and reuse it for subsequent logins. There may even be a way
to pool ldap connections.

> When use LDAP auth, Activemq should not always connect to ldap service to do authentication
> -------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6148
>                 URL: https://issues.apache.org/jira/browse/AMQ-6148
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.11.1
>            Reporter: JIE CHEN
>            Priority: Critical
>
> I am using LDAP service to do authentication for ActiveMQ, and I found everytime ActiveMQ
servers try to establish a connection between ActiveMQ client, the ActiveMQ server will create
a connection to LDAP server to do authentication. That's is not good, think about there are
thousands of ActiveMQ clients are trying to connect to ActiveMQ servers, the ActiveMQ servers
will need to create thousands of connections to LDAP servers. And moreover it is not reliable
as well because the connection between LDAP servers and ActiveMQ servers could be broken sometimes.
We need something similar as Cached LDAP Authorization Module. It is more reasonable that
the ActiveMQ will cache the ldap account credential in local memory and refresh in certain
interval.



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

Mime
View raw message