SignDoc Standard

This topic describes changes in the SignDoc Standard behavior since the previous release.

Removed certificate and biometric key warning icon

The yellow warning icon in the Manage Client is no longer visible for SignDoc users. SignDoc users with the ADMIN role will see the information in the section "System information" of the Administration view.

DefaultSigningHandler extended with configuration

SignDoc Standard provides advanced configuration options for digital PDF signatures. The DefaultSigningHandler in SignDoc Standard can now be configured with SignDoc SDK signature parameters. For example, this approach allows all signatures to be generated in the PAdES LTV signature format.

Logging

A built-in logging framework based on the Java Logging API is used for SignDoc Standard logs. The java-util-logging package provides the logging capabilities via the Logger class. The logging configuration parameters can be set via the GUI of the Administration Center or the SignDoc REST API.

Local time zone support

In this version, the time information is displayed in the local time zone on which the clients are running. User and account time zone information is removed from the UI and REST API.

S/MIME certificate configuration

The password of the certificate is requested when the certificate is uploaded.

Toggle on/off

The toggle representing the value of true/false for a setting is now described as on/off.

Extended external finish URL

This custom URL is called when a signing session is finished by the remote signer. The URL can be configured by placeholders for accountId, packageId and signerId that are automatically replaced by data (example: http://www.myserver.com/mypage.html?accountid=$ACCOUNT_ID&packageid=$PACKAGE_ID&signerid=$SIGNER_ID). If no URL is provided, the default finish page is displayed in the Signing Client.

Extended external resume later URL

This custom URL is called when a signing session is temporarily paused and resume later by the remote signer. The URL can be configured by placeholders for accountId, packageId and signerId that are automatically replaced by data (example: http://www.myserver.com/mypage.html?accountid=$ACCOUNT_ID&packageid=$PACKAGE_ID&signerid=$SIGNER_ID). If no URL is provided, the default finish page is displayed in the Signing Client.

Plugin class files

A plugin may now consist of more than a single class file.

Updated SignDoc Windows Service Installer

The JDBC URL no longer appears within quotation marks.

Changed button on document view

In the Document view header of the Signing Client, the following is changed for the Save button: the color is green, the text is replaced with DONE and the button now appears on the right.

Improved information when a package is not accessible for a recipient

The yellow warning icon in the Manage Client is no longer visible for SignDoc users. SignDoc users with the ADMIN role will see the information in the section "System information" of the Administration view.

Configurable SMTP configuration settings by account

Account administrators are able to set values for SMTP configuration using the Manage Client.

Final document generation no longer affects the display in the Signing Client

The spinning wheel is no longer displayed when the last recipient of a signing packet selects the "Finish" button. As a result, the Signing Client will close more quickly.

Discontinued REST API older versions

Starting with SignDoc 3.0.0, all remaining REST API calls for v2, v3 and v5 are discontinued. SignDoc requires v6 as the minimum version.

Audit Trail entries

The Audit Trail entries are modified to improve consistency with settings for various signing methods.

Final state of the signing session

Additional functionality was added so the signer cannot continue with the signing session in the final state when the remote signing URL is opened in more than one browser tab.

Content Security Policy (CSP) restricts execution of inline scripts

Inline scripts are now blocked by default when CSP header is set.