[
https://issues.apache.org/activemq/browse/AMQ-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41438#action_41438
]
Robin Bramley commented on AMQ-826:
-----------------------------------
The LDAPAuthorizationMap in 5.0.0 does not cope with composite destinations as
used by the advisory topics and was preventing producers sending messages.
ERROR LDAPAuthorizationMap - javax.naming.NameNotFoundException: [LDAP
: error code 32 - failed on search operation: uid=topic:]; remaining name 'uid=
topic://ActiveMQ.Advisory.TempQueue,topic://ActiveMQ.Advisory.TempTopic,ou=topics
,ou=destinations,o=ActiveMQ,ou=system'
Note that I'd changed the LogFactory call to use LDAPAuthorizationMap instead
of LDAPLoginModule...
Added the following code to the start of the getACLs method to make it usable:
//TODO: handle composite destinations properly
if(destination.isComposite()) {
ActiveMQDestination[] destinations =
destination.getCompositeDestinations();
// for now just check the first one
destination = destinations[0];
}
> LDAP based authorization support
> --------------------------------
>
> Key: AMQ-826
> URL: https://issues.apache.org/activemq/browse/AMQ-826
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: James Strachan
> Assignee: Nikola Goran Cutura
> Fix For: 5.2.0
>
> Attachments: ApacheDSEmbedded.zip, LdapAuth.zip
>
>
> Patch kindly added by ngcutura - discussion thread...
> http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
