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

   ### 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
   
   rocketmq 5.3.3
   
   ### JDK Version
   
   jdk 1.8
   
   ### Describe the Bug
   
   use cluster pxoxy mode and set proxy enableAclRpcHookForClusterMode = true,  
create a normal user
   producer and consumer use the normal user as accessKey and secretKey to send 
and consume message
   but i found proxy log  has some error, note that the normal user has no 
permisson to access system topic TBW102 and group CLIENT_INNER_PRODUCER 
   
   ### Steps to Reproduce
   
   use cluster pxoxy mode and set proxy enableAclRpcHookForClusterMode = true,  
create a normal user
   producer and consumer use the normal user as accessKey and secretKey to send 
and consume message
   but i found proxy log  has some error, note that the normal user has no 
permisson to access system topic TBW102 and group CLIENT_INNER_PRODUCER 
   
   ### What Did You Expect to See?
   
   normal user has permisson to access system topic and group
   
   ### What Did You See Instead?
   
   normal user don't have permisson to access system topic and group
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to