Skip to content

[Bug] Fix the permission check for retry topic to get topic route. #9072

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

Closed
3 tasks done
dingshuangxi888 opened this issue Dec 20, 2024 · 0 comments · Fixed by #9073
Closed
3 tasks done

[Bug] Fix the permission check for retry topic to get topic route. #9072

dingshuangxi888 opened this issue Dec 20, 2024 · 0 comments · Fixed by #9073

Comments

@dingshuangxi888
Copy link
Contributor

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

Linux

RocketMQ version

develop

JDK Version

JDK 8+

Describe the Bug

When a client fails to consume multiple times, a message is sent to the retry topic. If ACL 2.0 is used, querying the routing of the retry topic may result in a permission denied issue.

Steps to Reproduce

ACL permissions are configured only for specific Topic and Group permissions. When the client consumes sequentially and retries fail multiple times, observe whether the routing can be correctly obtained when sending retry messages.

What Did You Expect to See?

When obtaining the routing for the retry topic, authentication is performed according to the Group's permissions, and there is no need to separately authorize the retry topic.

What Did You See Instead?

When obtaining the routing for the retry topic, authentication is performed according to the Group's permissions, and there is no need to separately authorize the retry topic.

Additional Context

No response

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

Successfully merging a pull request may close this issue.

1 participant