Skip to content

[Bug] 5.x broker开启acl时,控台上重新发送消息错误 #9393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
aligege123 opened this issue May 8, 2025 · 1 comment
Open
3 tasks done

Comments

@aligege123
Copy link

aligege123 commented May 8, 2025

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • 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

Image

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初始化的RPCHookdoBeforeRequest

Image

但实际上将请求发送出去不用再验证自己发送的请求了

No response

@JKAK47
Copy link

JKAK47 commented May 8, 2025 via email

@aligege123 aligege123 changed the title [Bug] 5.x broker开启acl时,控台上重新发送错误 [Bug] 5.x broker开启acl时,控台上重新发送消息错误 May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants