[
https://issues.apache.org/jira/browse/ARTEMIS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908095#comment-14908095
]
ASF GitHub Bot commented on ARTEMIS-229:
----------------------------------------
Github user jmesnil commented on the pull request:
https://github.com/apache/activemq-artemis/pull/175#issuecomment-143239217
fwiw, Eclipse has the best document about evolving Java API and they use
the `2` version:
https://wiki.eclipse.org/Evolving_Java-based_APIs_3#.222.22_Convention
> 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)
