youngkermit8-coder opened a new issue, #1752: URL: https://github.com/apache/rocketmq-dashboard/issues/1752
### What happened? `AclService.createUser` rejects blank usernames, but `AclService.updateUser` accepts a non-null blank or whitespace-only username and persists it. This lets a partial update replace a valid ACL username with an invalid value. ### How to reproduce 1. Store an ACL user with a valid username. 2. Call `AclService.updateUser` with the stored ID and `username` set to whitespace (for example, `" "`). 3. Observe that `AclRepository.saveUser` receives a user whose username is whitespace. A focused `AclServiceTest` reproduces this deterministically on the current `rocketmq-studio` branch. ### Expected behavior When an update supplies `username`, blank or whitespace-only values should be rejected with a 400 business error and the repository should not be modified. A null username should continue to mean "leave the existing username unchanged" for partial updates. ### Duplicate check I searched open and closed issues and pull requests for `UpdateAclUserDTO username`, `ACL username blank`, `updateUser username ACL`, and `username cannot be blank ACL`; I did not find an existing report or contribution covering this update path. -- 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]
