Aias00 opened a new issue, #4161: URL: https://github.com/apache/rocketmq-dashboard/issues/4161
## Description Tencent Cloud RocketMQ roles are exposed in Studio as both ACL users and cluster-wide ACL rules. These are presented as separate resources with separate delete actions, but deleting a Tencent ACL rule currently calls the cloud `DeleteRole` API. This removes the underlying role account, including its access credentials, instead of only removing its read/write authorization. ## Steps to reproduce 1. Open the ACL page for a Tencent Cloud RocketMQ 5.x instance. 2. Create or select a role that has `PermRead` and/or `PermWrite` enabled. 3. Delete the role's entry from the ACL rules tab. 4. Refresh the ACL users tab or query the role in Tencent Cloud. ## Actual behavior The role account is deleted because `TencentAclService.deleteRule` calls `DeleteRole`, the same API used by the explicit ACL user delete operation. ## Expected behavior Deleting the ACL rule should revoke the role's cluster-wide read/write permissions while preserving the role account and its credentials. Only the ACL user delete action should call `DeleteRole`. Roles whose `PermRead` and `PermWrite` values are both disabled should no longer appear in the ACL rule list, but should remain visible in the ACL user list. ## Code location - `server/src/main/java/org/apache/rocketmq/studio/provider/tencent/TencentAclService.java` ## Proposed scope - Change Tencent rule deletion to call `ModifyRole` with `PermRead=false` and `PermWrite=false`. - Exclude roles with neither permission from `listRules`. - Add regression tests proving rule deletion preserves the role and user deletion remains the destructive operation. -- 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]
