Signing process loops asking for password and shows "certificate revoked" after signature request is sent

[julbroa]

Describe the bug

When attempting to sign a document using LibreSign in Nextcloud, the signing process enters a loop requesting the signing password, even though the password was already created previously. After selecting the document, choosing the signer, placing the visible signature field, and sending the signing request, the signing process starts. At that point, the app asks for the signing password. After entering the password, instead of completing the signature, it returns to the same password prompt screen. Additionally, a red warning message appears stating that the certificate is revoked. Even if a password is entered again, the process repeats and does not allow the document to be signed.

To reproduce

I'm an authenticated user

Go to "LibreSign" app in Nextcloud

Upload or select a PDF document

Select the user who will sign the document

Place the visible signature field in the document

Send the signing request

Proceed to sign the document

Enter the signing password

Confirm signing

The system returns to the password prompt screen

A red message appears indicating that the certificate is revoked

Expected behavior

After entering the signing password and confirming the signature, the document should be signed successfully. The system should not request the creation of a new signing password if one already exists, and it should not enter a loop. The certificate should remain valid and allow the signing process to complete normally.

Screenshots

Environment information

Versión
Nextcloud Hub 25 Autumn (32.0.6)
Sistema operativo: | Linux 6.8.0-90-generic x86_64
LibreSign
Versión 12.2.3
Docker installation

Additional context

No response