RockteMQ-AI commented on issue #11406: URL: https://github.com/apache/rocketmq/issues/11406#issuecomment-6142151481
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In `DefaultAuthorizationContextBuilder`, the `QUERY_MESSAGE` case builds the authorization context as a `Topic` resource (`Resource.ofTopic(...)`) without checking whether the topic is a retry topic. All sibling read paths (`VIEW_MESSAGE_BY_ID`, `PULL_MESSAGE`, `GET_MAX_OFFSET`, etc.) correctly map retry topics to `Resource.ofGroup(...)`, but `QUERY_MESSAGE` was missed. **Impact:** A consumer with a role granting `Group:<group>` + `SUB/GET` can pull, view, and consume retry messages but **cannot query them by key**. The `Resource.isMatch` check fails because `Topic:%RETRY%<group>` never matches a `Group:<group>` policy entry. **Severity:** Medium — affects all ACL 2.0 deployments that use retry topic key queries. The fix is a one-line change consistent with the existing pattern in sibling request codes. The reporter has indicated they will submit a PR for this issue. --- *Automated evaluation by RockteMQ-AI* -- 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]
