X-LightYear opened a new issue, #7246:
URL: https://github.com/apache/rocketmq-dashboard/issues/7246
## Problem
The ACL user directory REST endpoint accepts the same keyword filter that
the frontend API exposes, but the unpaged backend path ignores it.
## Reproduction
1. Configure an Apache ACL instance with users such as `orders-admin` and
`billing-reader`.
2. Call `GET /api/acl/users?instanceId=instance-a&keyword=billing`.
3. The frontend API sends this request when `listAclUsers({ keyword: billing
})` is used.
## Expected behavior
Only ACL users whose username or access key contains the keyword should be
returned, consistently with the existing paged ACL user search.
## Actual behavior
The controller accepted only `instanceId`, and `AclService.listUsers`
returned the full directory. Remote REST callers therefore received all users,
while mock mode applied the keyword locally.
## Root cause
The frontend/API contract declared `keyword` for `listAclUsers`, but
`AclController.listUsers` did not bind it and the unpaged service method had no
filter path.
## Testing
- `AclServiceTest.listUsersShouldApplyKeywordToTheUnpagedDirectory`
- `AclControllerTest.listUsersShouldForwardKeywordToTheDirectoryService`
- frontend ACL API contract test
- backend focused suite: 120 tests passed
- frontend focused suite: 7 tests passed
- frontend ESLint: 0 errors
- TypeScript/Vite compilation completed; repository license gate reports the
existing `toggle-selection` verification mismatch in this environment
Fixes #TEMP
--
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]
