Aias00 opened a new issue, #1989: URL: https://github.com/apache/rocketmq-dashboard/issues/1989
### Track RocketMQ Studio Track 1: unified control plane / ARCH-01 and AUTH-01. ### Problem Instance-scoped cluster discovery resolves the selected instance endpoint, but then executes the RocketMQ admin request directly through `MqAdminExtFactory` with a null RPC hook. That bypasses `RuntimeAdminClientResolver`, which is responsible for resolving the instance `adminCredentialRef` and injecting the ACL 1.0 `AclClientRPCHook`. Consequently, cluster list and cluster detail fail against an authenticated Apache instance even though other instance-scoped runtime pages use the configured credential correctly. ### Affected paths - `RocketMQClusterProvider.discoverClusters(instanceId)` - `RocketMQClusterProvider.refreshClusterDetail(clusterId, instanceId)` ### Expected behavior - Instance-scoped cluster reads execute through `RuntimeAdminClientResolver`. - The legacy no-instance path continues using the globally configured NameServer and anonymous/default admin client. - Existing cluster discovery error semantics remain unchanged. ### Acceptance criteria - Regression tests prove both instance-scoped list and detail use the runtime resolver. - Tests prove the instance path does not fall back to the anonymous factory call. - Legacy unscoped cluster discovery remains covered. ### Scope note This is distinct from #1449, which tracks reading ACL 2.0 policy resources. This issue concerns ACL 1.0 credentials on the cluster discovery transport itself. -- 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]
