Replies: 1 comment 4 replies
-
Adminweb should not hide anything, only if the search query does not produce a match in the database. Could be case sensitivity or something? To delete an old certificate you need to do it manually in the database. As one of the primary tasks of a CA is to keep track of issued certificates, it is not an exposed function to delete certificates (it would happen to easily by mistake). Removing a revoked certificate will of course make revocation lookups return "nothing found", and CRLs will not be populated with this entry. PS: Removing expired certificates is/will be possible with a service. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I have a strange problem: being logged in as SuperAdmin, I can find a revoked certificate via RA website, but not via adminweb website.
I noticed this problem when I revoked and deleted a certificate and wanted to issue a new one for the same user. I always got the message that the SubjectDN was already in use. As I did not find anything via adminweb I did not understand at first why this was happening. But then a collegue of mine searched for the DN via RA and found it! Interestingly, I cannot lookup the revoked certificate even by its serial number I found on the RA page via the adminweb page.
So, why is adminweb hiding it? How can this happen? And how can I now delete ALL references to old certificates, so that I can create a new one without the "SubjectDN already exists" problem?
Regards,
Holger
Beta Was this translation helpful? Give feedback.
All reactions