[
https://issues.apache.org/jira/browse/ARTEMIS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908057#comment-14908057
]
ASF GitHub Bot commented on ARTEMIS-229:
----------------------------------------
GitHub user jscheid opened a pull request:
https://github.com/apache/activemq-artemis/pull/175
ARTEMIS-229 validate user and role with address
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/waysact/activemq-artemis
ARTEMIS-229-validate-user-address
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/175.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 #175
----
commit 6890f126cbd3df6ef0b096d4f1256ef540b9b36f
Author: Julian Scheid <[email protected]>
Date: 2015-09-25T12:08:28Z
ARTEMIS-229 validate user and role with address
----
> Additional address argument for validateUserAndRole
> ---------------------------------------------------
>
> Key: ARTEMIS-229
> URL: https://issues.apache.org/jira/browse/ARTEMIS-229
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Julian Scheid
> Priority: Minor
>
> Making {{validateUserAndRole}} accept an extra {{address}} parameter and
> passing the destination address in {{SecurityStoreImpl.check}} (along with
> changing the cache keys accordingly) enables authorization schemes that take
> the destination address into account.
> To some degree this is already possible using the {{securityRepository}} but
> only for a static list of roles and destinations, it doesn't work so well in
> an environment where e.g. queues are created dynamically and need to be
> authorized based on the user's identity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
