Closed dschultz512 closed 1 week ago
Unfortunately I cannot reproduce this issue. Please provide more information:
Kai,
Thank you for the email.
As I have looked into the issue, it appears it is related to an expired intermediate certificate. Please see attached. I have created a new Intermediate CA and using it to create new certificates.
This was GitHub sending you my comment as an email. Please be aware that your response email was automatically published here.
Also, the attached screenshot has unfortunately been filtered out by GitHub.
Apologies. Screen shot below with expired intermediate certificate. And to clarify, I created the new Intermediate CA several months ago.
It appears I resolved the issue. There were several certificates in the KS that were using the expired Intermediate CA. Once I deleted them, I was able to create and save certificates. Thank you for your help.
It appears I resolved the issue. There were several certificates in the KS that were using the expired Intermediate CA. Once I deleted them, I was able to create and save certificates.
Good to hear that you could find a solution. The code that handles these things is in the JRE not in KSE, so there is nothing I can do about it anyway.
Describe the bug I have several certificates that have expired. I am able to delete them and create a new ones. But the updated certificate does not save to the keystore. When I create another certificate or re-open the keystone, the old expired certificate is shown.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots Newly created certificate
After closing and reopening keystore showing expire certificate
Environment