Hi James,
this check is based on a "workflow attribute" which you can find in the
table with the same name.
I dont know whats the reason for your WebUI timeout issue but you shoud
be able to pickup the old workflow (which is mentioned in the new
workflow as blocker) and use the controls to either finalise the request
or cancel ist. The cancel path will clear the attribute and you can
afterwards continue the new one. If your workflow is broken, there is no
other option then deleting the corresponing line from the database manually.
Oliver
On 09.05.24 20:43, James B. Byrne via OpenXPKI-users wrote:
Duplicate Key Error (Request)
The uploaded key was found to be used already by another certificate request
but it is not allowed to certify the same key twice.
The problem with this is that no certificates whatsoever have been issued from
this instance of openxpki. What occurred was that a certificate request was
started for this certificate but never completed due to the webui timing out.
Where does openxpki store the duplicate information in advance of completing
the signing request and how do I get rid of it?
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
