btlqql opened a new issue, #2185:
URL: https://github.com/apache/rocketmq-dashboard/issues/2185
### What happened?
Tencent ACL updates are routed from `UpdateAclUserDTO`, where only `id` is
required and permission fields are nullable for partial updates.
`TencentAclService.updateUser()` instead requires `username`, uses it as the
role identifier, and converts every omitted permission to `true`.
This causes two failures:
- a valid update such as `{id, permRead:false, permWrite:true}` is rejected
because `username` is absent;
- providing a username while omitting one permission silently enables that
permission instead of preserving its current value.
### Expected behavior
Use the required role id when no replacement username is supplied, and
preserve each existing Tencent role permission when that field is omitted from
the partial update.
### Reproduction
Update an existing Tencent role using only its `id`, or omit either
`permRead` or `permWrite`. The current backend rejects the first request and
resets omitted permission values to true in the second.
--
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]
