[ https://issues.apache.org/jira/browse/ARTEMIS-4754?focusedWorklogId=917275&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-917275 ]
ASF GitHub Bot logged work on ARTEMIS-4754: ------------------------------------------- Author: ASF GitHub Bot Created on: 02/May/24 11:35 Start Date: 02/May/24 11:35 Worklog Time Spent: 10m Work Description: gemmellr commented on PR #4916: URL: https://github.com/apache/activemq-artemis/pull/4916#issuecomment-2090279928 LGTM too. Might be best for e.g @jbertram to look before merge too, given the match change. Issue Time Tracking ------------------- Worklog Id: (was: 917275) Time Spent: 20m (was: 10m) > Make configuring security for AMQP federation user accounts simpler > ------------------------------------------------------------------- > > Key: ARTEMIS-4754 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4754 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: AMQP > Affects Versions: 2.33.0 > Reporter: Timothy A. Bish > Assignee: Timothy A. Bish > Priority: Major > Fix For: 2.34.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When creating the user account used to restrict access when securing an AMQP > federation account the currently implementation requires giving the > federation overly broad access so that it can create control and event queues > used for its internal mechanisms. We should make this easier and more narrow > so that a federation user can be granted access to a more limited set of > resources for internal federation mechanics besides access to those addresses > and queues which will be targets of federation. -- This message was sent by Atlassian Jira (v8.20.10#820010)