Aias00 opened a new issue, #2273: URL: https://github.com/apache/rocketmq-dashboard/issues/2273
## Problem The local ACL persistence path assumes that `rmq_acl_user.access_key` is unique, but the schema only enforces `username`. `createAndUpdatePlainAccessConfig` calls `selectOne(access_key)`, so duplicate rows can surface as `TooManyResultsException` rather than a controlled conflict. The same repository serializes ACL action and cluster collections with `String.join`. Null, blank, or duplicate elements can either fail serialization or create non-canonical persisted values. ## Scope - enforce `access_key` uniqueness for new database schemas and return a structured conflict when legacy duplicate data is encountered - normalize ACL action and cluster collections before local persistence: trim, remove null/blank entries, and deduplicate while retaining order - add focused regression tests ## Out of scope - remote broker ACL response tolerance is covered by #2256 - encrypted secret-key storage is a separate security remediation -- 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]
