[
https://issues.apache.org/jira/browse/ARTEMIS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908147#comment-14908147
]
ASF subversion and git services commented on ARTEMIS-229:
---------------------------------------------------------
Commit e85bb3ca4a75b0f1dfbe717ff90b34309e2de794 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=e85bb3c ]
This closes #175 ARTEMIS-229 address on Security Interface
> 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)
