Aias00 opened a new issue, #2681: URL: https://github.com/apache/rocketmq-dashboard/issues/2681
## Problem The K8s certificate renew endpoint extends the persisted validity dates by one year and marks the record valid, but it does not replace or parse the stored certificate/key material. Update requests cannot provide new PEM data either. The UI can therefore display a certificate as renewed while the actual credential remains expired. ## Evidence - `server/src/main/java/org/apache/rocketmq/studio/cluster/k8s/K8sCertController.java:49` - `server/src/main/java/org/apache/rocketmq/studio/cluster/k8s/K8sCertController.java:55` - `server/src/main/java/org/apache/rocketmq/studio/cluster/k8s/UpdateCertDTO.java:32` - `server/src/main/java/org/apache/rocketmq/studio/cluster/k8s/K8sCertService.java:147` ## Expected behavior - Renewal requires new certificate material and, where applicable, a matching private key. - Parse validity, issuer and SANs from the submitted certificate instead of manufacturing dates. - Reject invalid, expired or mismatched material. - Wire update/renew actions into certificate management UI with regression coverage. -- 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]
