dingshuangxi888 opened a new issue, #9072:
URL: https://github.com/apache/rocketmq/issues/9072

   ### Before Creating the Bug Report
   
   - [X] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq/discussions).
   
   - [X] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq/discussions)  of this 
repository and believe that this is not a duplicate.
   
   - [X] 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_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to