Cannot view some identities #48
-
Hello,
I have attached the exception stack trace from server.log. What is wrong with such identities and how can it be repaired? Regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hi Torsten, Wow, that is super weird. Well, the data in question got corrupted somehow – is this a database from a previous installation which has been upgraded? Fortunately the data in question isn't vital, it's stored in the Certificate Request History table as documented here: https://doc.primekey.com/ejbca/ejbca-operations/ejbca-ca-concept-guide/certificate-authority-overview/ca-fields#CAFields-UseCertificateRequestHistoryUse_Certificate_Request_History We don't actually recommend using this feature anymore, and you should fairly safely be able to remove the data from that table being simply performing a delete from CertReqHistoryData; on your database, but naturally please make a backup copy before doing so in case I may be entirely wrong =) Cheers, |
Beta Was this translation helpful? Give feedback.
-
Hello Mike, Where do I see the Certificate Request History within the GUI? Is this reflected by the "Identitiy -> Certificates View -> View Older/Newer"? Regards, |
Beta Was this translation helpful? Give feedback.
-
Hello Mike, Many thanks for your support and kind regards, |
Beta Was this translation helpful? Give feedback.
Hi Torsten,
Wow, that is super weird. Well, the data in question got corrupted somehow – is this a database from a previous installation which has been upgraded?
Fortunately the data in question isn't vital, it's stored in the Certificate Request History table as documented here: https://doc.primekey.com/ejbca/ejbca-operations/ejbca-ca-concept-guide/certificate-authority-overview/ca-fields#CAFields-UseCertificateRequestHistoryUse_Certificate_Request_History
We don't actually recommend using this feature anymore, and you should fairly safely be able to remove the data from that table being simply performing a
delete from CertReqHistoryData;
on your database, but naturally please make a bac…