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

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

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

Shannon Gallagher commented on ARTEMIS-1884:
--------------------------------------------

Hello,

Is there plans to start working on this feature?

I have encountered a need for message-level authorization, but am using Artemis (2.4.0). I have tried implementing the solution with remote interceptors, but am unable to extract the java subject from within the interceptor.

At this point, I think I would either need an Artemis feature similar to MessageAuthorizationPolicy in ActiveMQ 5 or some way to access the java subject from my interceptor.

PS Might I be asking this in the wrong place? Should I file a bug or feature ticket for interceptors to have access to the java subject? 

Thanks!

> 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)