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

   ### 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
   
   MacOS 13.2.1 (22D68)
   
   ### RocketMQ version
   
   5.3.4
   
   ### JDK Version
   
   1.8
   
   ### Describe the Bug
   
   broker:
   brokerClusterName = DefaultCluster
   brokerName = broker-a
   deleteWhen = 04
   fileReservedTime = 48
   flushDiskType = ASYNC_FLUSH
   namesrvAddr=127.0.0.1:9876
   storePathRootDir=data/store/broker-a
   
   enableControllerMode = true
   allAckInSyncStateSet = true
   controllerAddr = 127.0.0.1:9878
   
   authenticationEnabled = true
   authenticationProvider = 
org.apache.rocketmq.auth.authentication.provider.DefaultAuthenticationProvider
   initAuthenticationUser = {"username":"rocketmq","password":"12345678"}
   innerClientAuthenticationCredentials = 
{"accessKey":"rocketmq","secretKey":"12345678"}
   authenticationMetadataProvider = 
org.apache.rocketmq.auth.authentication.provider.LocalAuthenticationMetadataProvider
   authorizationEnabled = true
   authorizationProvider = 
org.apache.rocketmq.auth.authorization.provider.DefaultAuthorizationProvider
   authorizationMetadataProvider = 
org.apache.rocketmq.auth.authorization.provider.LocalAuthorizationMetadataProvider
   
   proxy:
   {
   "rocketMQClusterName": "DefaultCluster",
   "authenticationEnabled": true,
   "remotingListenPort": 8080,
   "grpcServerPort": 8081,
   "authenticationProvider": 
"org.apache.rocketmq.auth.authentication.provider.DefaultAuthenticationProvider",
   "authenticationMetadataProvider": 
"org.apache.rocketmq.proxy.auth.ProxyAuthenticationMetadataProvider",
   "innerClientAuthenticationCredentials": '{"accessKey":"rocketmq", 
"secretKey":"12345678"}',
   "authorizationEnabled": true,
   "authorizationProvider": 
"org.apache.rocketmq.auth.authorization.provider.DefaultAuthorizationProvider",
   "authorizationMetadataProvider": 
"org.apache.rocketmq.proxy.auth.ProxyAuthorizationMetadataProvider"
   }
   authorizationMetadataProvider 和 authorizationMetadataProvider 换成 
LocalAuthorizationMetadataProvider 和 LocalAuthenticationMetadataProvider 也一样
   
   ### Steps to Reproduce
   
   启动顺序:
   1. nameserver
   2.controller
   3.broker
   4.proxy
   
   ### What Did You Expect to See?
   
   
1.如何配置能实现不管是通过proxy连接,还是通过nameserver连接,都能进行授权验证?如果按照官网的文档https://rocketmq.apache.org/zh/docs/bestPractice/03access#%E6%9C%80%E4%BD%B3%E5%AE%9E%E8%B7%B5
 [存算分离架构调优] 配置,连接nameserver无需授权即可发消息
   2.如果broker不开启acl,等proxy正常启动创建完所需topic,再进行acl配置,proxy可以正常启动,这样有别的影响吗?
   
   ### What Did You See Instead?
   
   2025-12-24 22:58:26 ERROR main - create topic on broker failed. 
topic:TopicConfig [topicName=DefaultHeartBeatSyncerTopic, readQueueNums=1, 
writeQueueNums=1, perm=RW-, topicFilterType=SINGLE_TAG, topicSysFlag=0, 
order=false, attributes={}], broker:192.168.50.56:10911
   org.apache.rocketmq.client.exception.MQClientException: CODE: 16  DESC: 
username cannot be null.
   For more information, please visit the url, 
https://rocketmq.apache.org/docs/bestPractice/06FAQ
        at 
org.apache.rocketmq.client.impl.MQClientAPIImpl.createTopic(MQClientAPIImpl.java:474)
        at 
org.apache.rocketmq.proxy.service.admin.DefaultAdminService.createTopicOnBroker(DefaultAdminService.java:119)
        at 
org.apache.rocketmq.proxy.service.admin.DefaultAdminService.createTopicOnTopicBrokerIfNotExist(DefaultAdminService.java:85)
        at 
org.apache.rocketmq.proxy.service.sysmessage.AbstractSystemMessageSyncer.createSysTopic(AbstractSystemMessageSyncer.java:164)
        at 
org.apache.rocketmq.proxy.service.sysmessage.AbstractSystemMessageSyncer.start(AbstractSystemMessageSyncer.java:143)
        at 
org.apache.rocketmq.proxy.service.client.ClusterConsumerManager.start(ClusterConsumerManager.java:68)
        at 
org.apache.rocketmq.common.utils.AbstractStartAndShutdown.start(AbstractStartAndShutdown.java:33)
        at 
org.apache.rocketmq.common.utils.AbstractStartAndShutdown.start(AbstractStartAndShutdown.java:33)
        at 
org.apache.rocketmq.common.utils.AbstractStartAndShutdown.start(AbstractStartAndShutdown.java:33)
        at org.apache.rocketmq.proxy.ProxyStartup.main(ProxyStartup.java:93)
   2025-12-24 22:58:26 ERROR main - find an unexpect err.
   org.apache.rocketmq.proxy.common.ProxyException: create system broadcast 
topic DefaultHeartBeatSyncerTopic failed on cluster DefaultCluster
        at 
org.apache.rocketmq.proxy.service.sysmessage.AbstractSystemMessageSyncer.createSysTopic(AbstractSystemMessageSyncer.java:173)
        at 
org.apache.rocketmq.proxy.service.sysmessage.AbstractSystemMessageSyncer.start(AbstractSystemMessageSyncer.java:143)
        at 
org.apache.rocketmq.proxy.service.client.ClusterConsumerManager.start(ClusterConsumerManager.java:68)
        at 
org.apache.rocketmq.common.utils.AbstractStartAndShutdown.start(AbstractStartAndShutdown.java:33)
        at 
org.apache.rocketmq.common.utils.AbstractStartAndShutdown.start(AbstractStartAndShutdown.java:33)
        at 
org.apache.rocketmq.common.utils.AbstractStartAndShutdown.start(AbstractStartAndShutdown.java:33)
        at org.apache.rocketmq.proxy.ProxyStartup.main(ProxyStartup.java:93)
   
   ### 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