[
https://issues.apache.org/jira/browse/ARTEMIS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303974#comment-15303974
]
ASF GitHub Bot commented on ARTEMIS-537:
----------------------------------------
GitHub user dejanb opened a pull request:
https://github.com/apache/activemq-artemis/pull/544
ARTEMIS-537 - final improvements to OSGi integration and documentatio…
…n update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dejanb/activemq-artemis master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/544.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #544
----
commit d891e47774426e06b92c612fbc58bd098ef8f009
Author: Dejan Bosanac <[email protected]>
Date: 2016-05-27T11:51:21Z
ARTEMIS-537 - final improvements to OSGi integration and documentation
update
----
> Allow Artemis to use Karaf JAAS security
> ----------------------------------------
>
> Key: ARTEMIS-537
> URL: https://issues.apache.org/jira/browse/ARTEMIS-537
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: osgi
> Affects Versions: 1.2.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 1.3.0
>
>
> Right now Artemis can use only it's own role principal class when authorising
> clients. When used inside other container and leveraging their JAAS security
> implementation, we need to allow more flexibility in how we check client
> roles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
