Screen Location: Confluence Administration → Comala Document Management section → E-Signatures


This screen allows Confluence Admins to set the E-Signature Configuration option for workflow approvals. 

Each individual approval in a workflow can be edited to require user authentication. The global administrator specifies the type of authentication method that will be used.

Configuring e-signatures to use a signing token is compatible with SSO use for an instance.

User Signing Token Management

An individual user must set up an authentication app to generate time-based signing tokens - time-based one-time passwords (OTP). 

Each user who has set up a signing token app for the instance will be listed in the global E-Signature Configuration screen.

Users with active signing tokens will only be displayed when the requirement for the use of a signing token for identity authentication is set for the instance.

A global administrator can:

  • Remove an existing user signing token. This requires the user to re-initialize the authentication app for the instance.
  • Change Expiry date for the user's signing token. This requires the user to re-initialize the authentication app for the instance when the expiration date is reached.

If a user's signing token expiration date is reached the user will continue to be listed in the global E-Signatures Configuration screen with the expired date displayed. The user will be displayed only until they next open an approval.

After the user logs in, they will need to re-initialize the signing token using an authentication app.

Credentials Security

The e-signature process will submit the username and approval signing token through Comalatech's secure server without storing these details.

For usability, user validation for the credentials is provided against previous, current and the next calculated signing token generated by the authenticator app.