We use Certificate Manager (Domino 12.0.2) to manage SSL certificates. They are imported from a 3rd party CA and seem to be working fine. We do this once a year, as the certificates must be renewed annually. When I import new certificates, the server still uses the old certificate (which expires in a few days).
How do I force the server to use the new certificate without deleting the old one (in case something goes wrong)?
If I just do nothing, will the server start using the new certificate when the old one is marked as expired ?
It seems you have created a new TLS Credentials document and created a new CSR and got certificates based on the new CSR that you imported in certificate store database. You must have requested the certificate for the same host name. Is that correct?
If my understanding is correct then you can take backup of certstore.nsf database and you can delete the old TLS Credentials document so that new one will start taking effect immediately.
You can also check certificate information using 'tell certmgr show certs'. This should show you active TLS Credentials in certificate store database.
The problem is not the switch from keyring file to certstore - that has been working for 2 years. The problem is switching to new certificate with same hostname. Will the new one become the active one when the old one expires ?
Having the duplicate TLS credentials with the same host name is not recommended. If the new certs is valid before the date of the old certificate expiry. Then you could delete the old TLS certs and have the new TLS cert document in the certstore database that should work.
Please have the backup of the certsore.nsf before deleting the old certs. Thank you.
So you have both the suggestion if it continues to work after current cert expiration. You can delete the expired one. If it doesn't work you can delete the old and keep the new TLS document in the certstore which from the third party.
I was curious about this too a few months ago. I waited until the certificate expired at 6:59:59pm and reloaded the web page after about 5 minutes. The new cert was being used automatically! A few days later I deleted the expired cert in Certificate Manager.
I also noticed this entry in the server log around the time of the change:
I know this question is old and has an accepted answer. However, I believe I have a better option for "forcing the server to use the new certificate without deleting the old one".
After you have issued the new certificate, you can set the Status field of the old certificate to "Archived". This almost immediately updates the certificate store, and removes that certificate from the list. You can easily set it back to "Issued" if there is a problem.