[
https://issues.apache.org/jira/browse/ARTEMIS-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197768#comment-17197768
]
Ryan Yeats commented on ARTEMIS-1884:
-------------------------------------
I am looking for a feature like this in Artemis or at least the ability to add
a plugin to incorporate this feature and have investigated 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]
The beforeDelivery method call however is not suitable for this use case
because the call happens after the broker has decided the consumer can handle
the message and it does not have direct access to the Subject of the
MessageConsumer in order to make a policy decision.
[~jbertram] I would work on a PR to extend the plugin API to be able to make it
useful for this kind of feature but its hard to tell from your last response if
it would be received well. I think it would be enough to add an additional
plugin extension point in ServerConsumerImpl for the handle method to allow for
plugins to determine if a consumer should receive a given message.
> 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
(v8.3.4#803005)
