[
https://issues.apache.org/jira/browse/AMQ-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458615#comment-13458615
]
Claus Ibsen commented on AMQ-3883:
----------------------------------
Hmm in Camel we had an issue with hadoop (its hdfs). I think that the principal
on the current thread should be sufficient to be accepted. This is what I have
seen in other frameworks.
So the code proposed by Raj, may see as a good idea.
If ever other framework have to create a special activemq-jaas-xxx component
then that is not a good direction.
> activemq-jaas authorization doesn't work with Karaf JAAS LoginModule
> --------------------------------------------------------------------
>
> Key: AMQ-3883
> URL: https://issues.apache.org/jira/browse/AMQ-3883
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.6.0
> Reporter: Freeman Fang
> Attachments: AMQ-3883.patch
>
>
> currently activemq-jaas can't work with karaf loginModule, the reason comes
> from the compare between
> amq GroupPrincipal and karaf UserPrincipal/RolePrincipal doesn't work
> More details please see[1].
> We have a similar issue in Servicemix NMR[2] and the fix can honor the
> compare between
> amq GroupPrincipal and karaf UserPrincipal/RolePrincipal yet not introduce
> any dependency between activemq-jaas and karaf jaas.
> [1]http://karaf.922171.n3.nabble.com/Karaf-ActiveMQ-authorization-problem-td4024834.html
> [2]https://issues.apache.org/jira/browse/SMX4NMR-283
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
