Hello,

Using dockerized OpenXPKI in v3.32.8 and unmodified workflows (but small 
changes in profiles) from openxpki-config/community in version 
0b140fd441d4a61cbdd2f303b60942462114977d.

We are experiencing the following issue: When a certificate revocation request 
for a valid, issued certificate is created in the Webinterface, the workflow 
fails with the message "Unable to load workflow information." displayed in the 
Webinterface. Workflow history looks like this:

> 2026-03-24 10:35:27   INITIAL crr_initialize  EXECUTE hbaum   7e3a28e67f7f
> 2026-03-24 10:35:27   INITIAL_CRR_INITIALIZE_0        
> crr_set_workflow_attributes     AUTORUN hbaum   7e3a28e67f7f
> 2026-03-24 10:35:27   CHECK_BATCHMODE global_noop     AUTORUN hbaum   
> 7e3a28e67f7f
> 2026-03-24 10:35:28   PENDING_USER    crr_submit      EXECUTE hbaum   
> 7e3a28e67f7f
> 2026-03-24 10:35:28   CHECK_NOTIFY    crr_submit      EXCEPTION: State 
> 'CHECK_NOTIFY' should be automatically executed but there are no actions 
> available for execution.      hbaum   7e3a28e67f7f

and server catchall.log with loglevel TRACE says this:

> 2026/03/24 10:36:13 
> OpenXPKI.Server.Workflow.Condition.CertificateHasStatus.ERROR 
> configuration_error exception thrown from 
> [OpenXPKI::Server::Workflow::Condition::CertificateHasStatus: 29; before: 
> OpenXPKI::Server::Workflow::Condition: 51]: certificate has status expected 
> status missing or invalid [pid=7956|sid=nlUZ]
> 2026/03/24 10:36:13 
> OpenXPKI.Server.Workflow.Condition.CertificateHasStatus.ERROR 
> configuration_error exception thrown from 
> [OpenXPKI::Server::Workflow::Condition::CertificateHasStatus: 29; before: 
> OpenXPKI::Server::Workflow::Condition: 51]: certificate has status expected 
> status missing or invalid [pid=7956|sid=nlUZ]
> 2026/03/24 10:36:13 openxpki.system.ERROR Attempt to execute activity on 
> workflow that is not in proc_state "manual"; __activity__ => crr_submit, 
> __proc_state__ => exception, __wf_id__ => 30463 [pid=7956|sid=nlUZ]

When a revocation is requested via RPC, the log says this:

> 2026/03/24 10:42:55 openxpki.auth.INFO Login successful (user: Anonymous, 
> role: System) [pid=8413|sid=Sf+a]
> 2026/03/24 10:42:56 Workflow.State.ERROR workflow_error exception thrown from 
> [Workflow::State: 164; before: Workflow: 338]: State 'CHECK_BATCHMODE' should 
> be automatically executed but there are multiple actions available for 
> execution. Actions are: global_check_authorized_signer, global_noop2 
> [pid=8413|sid=Sf+a]
> 2026/03/24 10:42:56 openxpki.workflow.ERROR Workflow 
> 31487/certificate_revocation_request_v2/CHECK_BATCHMODE uncaught exception 
> [pid=8413|sid=Sf+a]
> 2026/03/24 10:42:56 openxpki.system.ERROR 
> I18N_OPENXPKI_SERVER_WORKFLOW_ERROR_ON_EXECUTE; __ACTION__ => 
> crr_set_workflow_attributes, __ERROR__ => State 'CHECK_BATCHMODE' should be 
> automatically executed but there are multiple actions available for 
> execution. Actions are: global_check_authorized_signer, global_noop2, 
> __EXCEPTION__ => Workflow::Exception [pid=8413|sid=Sf+a]
> 2026/03/24 10:42:56 openxpki.workflow.ERROR Error executing workflow activity 
> "crr_initialize" on workflow id #31487 (type 
> "certificate_revocation_request_v2"): 
> I18N_OPENXPKI_SERVER_WORKFLOW_ERROR_ON_EXECUTE; __ACTION__ => 
> crr_set_workflow_attributes, __ERROR__ => State 'CHECK_BATCHMODE' should be 
> automatically executed but there are multiple actions available for 
> execution. Actions are: global_check_authorized_signer, global_noop2, 
> __EXCEPTION__ => Workflow::Exception [pid=8413|sid=Sf+a]

This issue was IIRC not present before updating our workflows to 
0b140fd441d4a61cbdd2f303b60942462114977d. Is there any other information that I 
can provide?

Thank you for all your work on OpenXPKI and your consideration.

Best regards,
Herbert



_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

Reply via email to