[
https://issues.apache.org/jira/browse/ARTEMIS-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308213#comment-17308213
]
Clebert Suconic commented on ARTEMIS-3205:
------------------------------------------
Message are usually scheduled for a reason... if you regret scheduling it, the
only way to do is through a management operation.
Any other API you put on top of the broker would be another APi. you could have
users connecting to the broker for that.
We are not sure how you would do such thing. What APIs to expose? Management is
just enough for that.
You could expose a Jolokia script calling the operations you want on the broker.
If you have some ideas on what to implement to do what you want, I am open to
hear... otherwise there is no way to implement what you are asking. As Justin
said a Queue system is not a CRUD like a database.
> Scheduled messages should not require management user
> -----------------------------------------------------
>
> Key: ARTEMIS-3205
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3205
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.17.0
> Reporter: Stefan
> Priority: Major
> Labels: security
>
> We are currently trying to implement a scheduled message use-case with
> Artemis where deleting scheduled messages is sometimes necessary.
> However, we could not find any solution to dequeue scheduled messages before
> they are routed to the queue without using a management user (i.e. via
> QueueControl or JMX-Operations).
> Is this the only way it can be done in Artemis?
> We have concerns about this configuration, because our client implementation
> needs admin user rights to handle 'simple' CRUD operations. Regarding DB
> clients, this is a common antipattern.
> Shouldn't this also be possible for standard users for reasons of security?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
