SignDoc Standard

GlobalSignDigitalSigning Handler - mTLS keystore password incorrect on Windows

1800593: The login into GlobalSign DSS attempt failed if the certificate has more than one encryption in PKCS7 Encrypted data.

Expiration Issue of Signing Packages

1800592: The expired status of a signing package was not updated for packages when another package from a list of expired packages was corrupted.

Character corruption - Attached File in Complete Email

1800588: Japanese characters in file names of email attachments of the Complete Email were corrupted.

GlobalSignDigitalSigningHandler - UTF-8 multibyte characters do not work in dynamic common name

1800589: If the signer name contains multi-byte characters, e.g. Japanese characters, the Common Name of the signing certificate issued by GlobalSign will be populated with the signer ID in Japanese characters instead of the specified signer name.

Spring4Shell vulnerability

1792897: SignDoc Standard includes the fix for Spring4Shell Vulnerability (CVE-2022-22965).

Loading a signing certificate

1762587: A signing certificate could not be loaded in a Windows environment.

Sending signing package and signer states to Kofax TotalAgility

1733783: The updated signing package and signer states were not sent to Kofax TotalAgility in case of Kofax TotalAgility re-connect.

Serialization of StateChangeEventSigner

1732914: The serialization of StateChangeEventSigner did not work for the Package Archiver.

Issue with statistics page in installations consisting of one account

1731040: The Administration Center Statistics page for the system with one account showed an empty list when selecting from the drop down list "Please select users".

Issue with file names of email attachments

1730716: File names of documents attached to the last email included character combinations consisting of a backslash followed by a letter or by a combination of digits when non-Latin symbols were used.

Issue detecting recipient's preferred language in a common signing session

1730253: The Signing Client did not recognize the recipient language with country code when using the common signing session.

Issue with signingMode for signed signature field

1695505: Signed signature fields had no signingMode attribute set when the containing document was retrieved via REST.

Multiple unsolicited sending of invitations for signing

1692802: Signers of signing packages were notified multiple times when the order of recipients was set to sequential signing.

Issue with remote signing link

1681214: The generation of remote signing links led to an error for completed signing packages whose signers had to be externally authenticated.

Issue with package state change complete

1676770: The package state change event did not inform the user when the signing package had been completed.

Invalid expiration date

1675181: Signing packages were successfully created and moved to the PREPARED state even if the expiry date was in the past.

Delegation of signing requests not shown in audit trails

1671022: The audit trail did not contain entries about forwarding the signing request to another person.

Failed upgrade procedure

1662564: The process to upgrade a SignDoc 2.2 to a newer version failed due to missing manual configuration settings.

No error messages for invalid image type

1602072: If images uploaded for signing were not in a supported format, no error message was displayed.

Ignored maximum size of packages for accounts

1591276: The account-specific value cirrus.document.prepare.size.max was ignored when a package was created via REST v7. The global (application-wide) value was used instead.

Issue with zoom in and out in documents

1370061: In the signing view, the document could not be zoomed in and out.

Issue with document preparation on iPad Pro

1351553: While editing a text field using the Prepare Document view on an iPad Pro, the focus jumped to another field in the document.