[
https://issues.apache.org/jira/browse/ARTEMIS-4582?focusedWorklogId=906994&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-906994
]
ASF GitHub Bot logged work on ARTEMIS-4582:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Feb/24 16:51
Start Date: 26/Feb/24 16:51
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4820:
URL:
https://github.com/apache/activemq-artemis/pull/4820#issuecomment-1964633266
a question. the object name for an queue, Q1::Q1:
org.apache.activemq.artemis:broker="localhost",component=addresses,address="Q1",subcomponent=queues,routing-type="anycast",queue="Q1",
maps nicely to:
jmx.queues.Q1::Q1
But should it be `jmx.queue.` the management messages use the resource name
queue rather than queues. The MbeanObject name use attribute
subcomponent=queues, queue=x. I guess it should be queue. No point polluting
the settings with plurals when not necessary.
Issue Time Tracking
-------------------
Worklog Id: (was: 906994)
Time Spent: 1h (was: 50m)
> add view and update permissions to augment the manage rbac for control
> resources
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-4582
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4582
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker, Configuration, JMX, Web Console
> Affects Versions: 2.31.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> we have the manage permission that allows sending to the management address,
> to access any control resource. We don't however distinguish what a user can
> do.
> We should segment control operations into categories: CRUD provides a basis
> view for get/is (Read)
> update for set or operations that mutate or modify.
> We allow this sort of configuration via management.xml for jmx mbean access
> but using a different model based on object name.
> All of the mbeans delegate to the control resources.
> If we add these two additional permissions then we can have a single rbac
> model (that supports config reload) and more granularity on control resource
> access from the management address.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
