X-LightYear opened a new issue, #5021:
URL: https://github.com/apache/rocketmq-dashboard/issues/5021

   ## Problem
   
   The Studio already supports updating ACL users through the authenticated 
REST endpoint `/api/acl/users/update`. `AclService.updateUser` implements 
partial updates for Apache-backed users and delegates Tencent role updates to 
`TencentAclService.updateUser`.
   
   The MCP catalog exposes `rmq.user.list`, `rmq.user.get`, `rmq.user.create`, 
and `rmq.user.delete`, but has no `rmq.user.update` tool. An operator or agent 
can therefore inspect, create, and remove ACL identities through MCP, but 
cannot complete the existing user-management lifecycle without falling back to 
REST.
   
   ## Existing capability
   
   - `AclController.updateUser` accepts `UpdateAclUserDTO`.
   - `AclService.updateUser` preserves omitted fields and existing credentials 
for Apache users.
   - Tencent role updates are delegated to `TencentAclService.updateUser`.
   - The web ACL page already calls `updateAclUser` for username, admin, 
cluster-scope, and Tencent permission changes.
   - Existing MCP ACL mutations use the guarded `MutationToolHandler` 
dry-run/confirm flow and project responses through `AclUserItem`, which 
excludes credentials.
   
   ## Expected behavior
   
   Expose a guarded `rmq.user.update` MCP mutation that reuses 
`AclService.updateUser`, supports the fields already accepted by the REST 
contract, keeps credentials out of the output, and is authorized with the same 
`acl:write` / ACL capability boundary as the existing user mutations.
   
   The response should use the existing safe `AclUserItem` projection and 
preserve provider-specific identifiers and partial-update semantics.
   
   ## Scope
   
   Add the MCP input contract, mutation handler, catalog entry, and 
deterministic contract/handler coverage. Do not change REST or service behavior.


-- 
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]

Reply via email to