You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Johan Stenberg (JIRA)" <ji...@apache.org> on 2018/05/24 10:29:00 UTC

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

     [ https://issues.apache.org/jira/browse/ARTEMIS-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Stenberg updated ARTEMIS-1884:
------------------------------------
    Summary: ActiveMQ5-like message-level authorization  (was: ActiveMQ 5 like message-level authorization)

> 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
>    Affects Versions: 2.6.0
>            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)