[jira] [Comment Edited] (ARTEMIS-1884) ActiveMQ5-like message-level authorization

["Shannon Gallagher (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660812#comment-16660812 ] 

Shannon Gallagher edited comment on ARTEMIS-1884 at 10/23/18 3:23 PM:
----------------------------------------------------------------------

Wasn't sure if the remote interceptor not having access to the subject was as designed or a potential miss. Perhaps I'll submit a new feature request for the -remote interceptor- connection.

Thanks for the info :) 

 


was (Author: sgalla):
Wasn't sure if the remote interceptor not having access to the subject was as designed or a potential miss. Perhaps I'll submit a new feature request for the remote interceptor.

Thanks for the info :) 

> ActiveMQ5-like message-level authorization
> ------------------------------------------
>
>                 Key: ARTEMIS-1884
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1884
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Johan Stenberg
>            Priority: Major
>
> In ActiveMQ 5 we have [MessageAuthorizationPolicy|https://activemq.apache.org/maven/apidocs/org/apache/activemq/security/MessageAuthorizationPolicy.html]. We would need a similar feature in Artemis to being able to migrate to it.
> In Artemis exists the [ActiveMQServerPlugin#beforeDeliver|https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/plugin/ActiveMQServerPlugin.java#L502] callback method were we probably could prevent message delivery by throwing an exception but using exceptions for flow control feels like a very wrong thing to do here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)