[Bug] 5.x broker开启acl时,控台上重新发送消息错误
- Dominant language
- Java
- Stars
- 22.6k
- Forks
- 12k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 26
Description
### 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
Windows 11
### RocketMQ version
5.2.0
### JDK Version
_No response_
### Describe the Bug

### Steps to Reproduce
1.broker开启acl(acl1.0,不是新推出的2.0)
2.启动消费者,用dashboard发送一条消息并消费
3.在dashboard将消息查询出来后点击重新发送
### What Did You Expect to See?
重新发送成功
### What Did You See Instead?
org.apache.rocketmq.client.exception.MQClientException: CODE: 1 DESC: invoke consumer <10.208.62.32@102914> Exception: org.apache.rocketmq.acl.common.AclException: Check signature failed for accessKey=admin_user, org.apache.rocketmq.acl.plain.PlainPermissionManager.validate(PlainPermissionManager.java:629) For more information, please visit the url, https://rocketmq.apache.org/docs/bestPractice/06FAQ
### Additional Context
从broker端debug看是因为broker将消息发送给客户端时又重新调用了acl初始化的`RPCHook`的`doBeforeRequest`

但实际上将请求发送出去不用再验证自己发送的请求了
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.