Overview
Depending on the workflow approval configuration, you may be required to confirm your identity prior to taking part in a content review by providing either:
- your password or a signing token
- your username and password or signing token.
Approvals are configured individually to require identity authentication.
The user credentials prompt is added to the workflow popup in the state with the approval.
This is most commonly implemented for statutory compliance purposes.
The Approve and Reject buttons are disabled until you enter the requested credentials.
On entering the username and password, the buttons will become active. The reviewer can then mouse-over each review button to display the destination state.
Credentials will be checked by the server when either the Approve or Reject button is pressed.
Failed login attempts will be logged in server logs and the Confluence Audit Log. If a signing token was required the failed attempt is also logged in the global E-Signatures Configuration screen.
An individual approval can be edited by a content editor to require credentials for a user and will add the credentials prompt to the workflow popup for the approval.
- the required credentials (password or signing token) are set by a global administrator in the Comala Document Management E-Signatures Configuration screen.
- if authentication requires a signing token each user will have to set up a personal code using a third-party authentication app.
See also
- Reviewer Authentication
- Reviews
- Roles and Permissions
- E-Signatures
- {approval} macro - Reviewers /Assignees
credentialsparameter