You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Linux
RocketMQ version
develop
JDK Version
JDK 8+
Describe the Bug
When a client fails to consume multiple times, a message is sent to the retry topic. If ACL 2.0 is used, querying the routing of the retry topic may result in a permission denied issue.
Steps to Reproduce
ACL permissions are configured only for specific Topic and Group permissions. When the client consumes sequentially and retries fail multiple times, observe whether the routing can be correctly obtained when sending retry messages.
What Did You Expect to See?
When obtaining the routing for the retry topic, authentication is performed according to the Group's permissions, and there is no need to separately authorize the retry topic.
What Did You See Instead?
When obtaining the routing for the retry topic, authentication is performed according to the Group's permissions, and there is no need to separately authorize the retry topic.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Linux
RocketMQ version
develop
JDK Version
JDK 8+
Describe the Bug
When a client fails to consume multiple times, a message is sent to the retry topic. If ACL 2.0 is used, querying the routing of the retry topic may result in a permission denied issue.
Steps to Reproduce
ACL permissions are configured only for specific Topic and Group permissions. When the client consumes sequentially and retries fail multiple times, observe whether the routing can be correctly obtained when sending retry messages.
What Did You Expect to See?
When obtaining the routing for the retry topic, authentication is performed according to the Group's permissions, and there is no need to separately authorize the retry topic.
What Did You See Instead?
When obtaining the routing for the retry topic, authentication is performed according to the Group's permissions, and there is no need to separately authorize the retry topic.
Additional Context
No response
The text was updated successfully, but these errors were encountered: