caton-wang opened a new issue, #9139:
URL: https://github.com/apache/rocketmq/issues/9139

   ### 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
   
   OS: Any linux
   
   ### RocketMQ version
   
   Release 5.3.0
   
   ### JDK Version
   
   Oracle JDK 1.8
   
   ### Describe the Bug
   
   When disable ACL  2.0 authorization in broker.conf config file, normal user 
can not see and access topic created by super user in 5.3.0.  although 
authorization has been disabled, you have to run following ACL rule, to grant 
the normal user access the topic create by super user:
   
   
![Image](https://github.com/user-attachments/assets/b1f04e27-cb56-4800-9f15-ea96c4cd441b)
   
   ### Steps to Reproduce
   
   1. Disable authorizaiton parameters in broker.conf.
   2. Create a normal user.
   3. Create a topic use super user.
   4. Produce and consume by using this normal user.
   
   ### What Did You Expect to See?
   
   Normal user can produce and consume rightly when authorization disabled.
   
   ### What Did You See Instead?
   
   Normal user can not see and access topic created by super user when 
authorization disabled.
   
   ### 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