Credentials prompt
- Technical Communications
- Robert Alexander Marshall
Overview
Depending on the workflow approval configuration, you can 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.
A workflow editor can edit an individual approval to require user authentication using the workflow builder.
Credentials prompt
The user credentials prompt is added to the workflow state dialog box in the state containing the approval.
This is most commonly implemented for statutory compliance purposes.
The Approve and Reject buttons are unavailable (greyed out) 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 are checked when either the Approve or Reject button is pressed.
Failed login attempts are logged in the Confluence audit log. If a signing token was required, the failed attempt is also logged in the e-signatures global configuration screen.
Required type of credentials (Confluence username and password, Confluence password, or signing token) is set by a global administrator in the app global e-signatures configuration screen
If authentication requires a signing token, each user must set up a personal code using a third-party authentication app.
See also
Need support? Create a request with our support team.