-
-
Notifications
You must be signed in to change notification settings - Fork 203
Closed
Labels
area/aclscope/backendRelated to backend changesRelated to backend changesstatus/triage/completedAutomatic triage completedAutomatic triage completedtype/bugSomething isn't workingSomething isn't working
Milestone
Description
Issue submitter TODO list
- I've looked up my issue in FAQ
- I've searched for an already existing issues here
- I've tried running
main-labeled docker image and the issue still persists there - I'm running a supported version of the application which is listed here
Describe the bug (actual behavior)
When creating an ACL for consumers using the dedicated form, it only assigns the READ permission for the group. In many cases, this is insufficient because some consumer groups also require the DESCRIBE permission to discover the members of the group. As a result, users frequently encounter "Group authorization denied" errors and have to manually add another ACL for DESCRIBE.
Expected behavior
The form should automatically add the DESCRIBE permission for consumer groups by default when assigning READ. This would prevent common authorization issues and allow users to restrict access by group name if necessary.
Your installation details
.
Steps to reproduce
- Add an ACL for a consumer group using the 'ACL for consumers' form.
- Only the READ permission is added for the group.
- Attempt to use the consumer group and see that it fails with a "Group authorization denied" error in some cases.
- Add a separate ACL for DESCRIBE to resolve the issue.
Screenshots
No response
Logs
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
area/aclscope/backendRelated to backend changesRelated to backend changesstatus/triage/completedAutomatic triage completedAutomatic triage completedtype/bugSomething isn't workingSomething isn't working