btlqql opened a new issue, #2254: URL: https://github.com/apache/rocketmq-dashboard/issues/2254
## Problem Kubernetes certificate SAN entries are currently accepted and persisted without element-level validation or normalization. Null, blank, whitespace-padded, and duplicate values can therefore enter the database. Legacy rows with null entries are returned unchanged, and the certificate list's client-side search calls string methods on every SAN entry, so one malformed entry can break certificate discovery. ## Expected behavior Certificate SAN values should be canonical at the persistence boundary: - create and update requests reject null or blank list elements; - stored values are trimmed, blank values are removed, and duplicates are removed while retaining their first-seen order; - existing rows with legacy null/blank/duplicate values are normalized when read. ## Proposed scope Add element-level Bean Validation to both certificate request DTOs, normalize SAN lists on repository reads and writes, and add focused validation and persistence tests. I searched existing issues and pull requests for K8s certificate SAN validation, blank/duplicate SAN entries, and null SAN search failures. I also checked the five target paths against all open `rocketmq-studio` pull requests; no duplicate report or file collision was found. -- 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]
