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

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-1884:
----------------------------------------------------------

Commit 86a2cad12ac77cc50ff5841c87d5d15865f983c3 in activemq-artemis's branch refs/heads/master from Ryan Yeats
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=86a2cad ]

 ARTEMIS-1884 add plugin API for message level authorization policies


> 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
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)