Overview
The Enforce identity authentication feature defines the trigger events that prompt a recipient to re-authenticate when interacting with an agreement. There are three independently selectable options:
- Authenticate when opening the agreement.
- Authenticate when applying a signature.
- Authenticate when completing the agreement.
The triggers that are enabled encompass all signers included in the agreement (internal and external).
Availability:
Enforce identity authentication is limited to enterprise license plans.
Configuration scope:
The features can be enabled at the account and group levels.
How it's used
Prerequisites
Enforce identity authentication supports the following recipient authentication methods:
Choose the authentication method that meets the requirements of your signing workflow and organization.
Phone authentication and One-Time Password via Email aren't supported for agreements signed in an embedded iframe when an Enforce identity authentication challenge is enabled. Use a non-embedded signing experience for these agreements.
If another authentication method is assigned to a recipient, the agreement proceeds normally, but Enforce identity authentication doesn't apply to that recipient.
The recipient experience
The recipient is presented with the authentication UI upon triggering an authentication challenge.
The supported authentication methods are:
- Phone authentication - An SMS-based text that provides a five-digit code that the signer must enter before affixing the signature
- Acrobat Sign authentication - A request to authenticate to Acrobat Sign through the Adobe identity management system. Acrobat Sign authentication requires the recipient to authenticate through the Adobe identity management system. Consider whether recipients have access to an appropriate Adobe identity when selecting this method.
Recipients that authenticate using the Acrobat Sign authentication method must authenticate through the Acrobat identity management system. All social authentication options (Google, Facebook, and Apple) are removed during the authentication process.
Accounts that configure their Admin Console organization to allow SSO authentication will authenticate against their configured identity provider, removing the requirement for their internal recipients to be entitled with a license for Acrobat Sign.
Once the authentication is passed, the recipient can continue the form-filling/signing process.
- One-Time Password via Email - A password is sent to the recipient's email address that must be entered to gain access to interact with the agreement.
Because the password is sent to the same email address as the recipient's email notification, this authentication method only serves as a single-factor authentication method. This may be acceptable for some use cases (such as internal recipient workflows). Because the verification code is sent to the same email address as the agreement notification, Email OTP provides single-factor authentication. Organizations that require additional identity assurance can use it with a TSP-backed digital signature when appropriate for their workflow.
Configuration
To enable Enforce identity authentication options, navigate to Bio-Pharma Settings > Enforce identity authentication.
Enforce identity authentication contains three independently selectable options:
- Challenge the user to authenticate themselves when the agreement is opened - When enabled, each recipient must authenticate before the agreement is opened for viewing.
- Challenge the user to authenticate themselves when the signer clicks a signature field in the agreement - When enabled, all recipients must authenticate every time a signature field is selected (before the signature can be applied).
- Only signature and signature block fields are re-authenticated; initial fields are not.
- The setting impacts both required and optional signature and signature block fields.
- Challenge the user to authenticate themselves when the Click to Sign button is selected after the signing ceremony is complete - When enabled, the recipient must reauthenticate after selecting the Click to Sign button (when they have completed their interaction with the agreement).
Related settings
The option to Challenge the user to authenticate themselves when the agreement is opened can be suspended for recipients in your account if they are logged in to Acrobat Sign when the agreement is opened. This can eliminate some of the friction for your internal signers.
To allow your users to skip the agreement opening authentication if logged in:
- Navigate to Account Settings > Send Settings > Signer Identification Options.
- Enable Don’t challenge the signer to re-authenticate if they are already logged in to Acrobat Sign.
- Save the page configuration.
Audit report changes
When any of the Enforce identity authentication options are enabled, the audit report explicitly logs every authentication in the audit report, and to a lesser degree, in the activity panel of the agreement.
Things to keep in mind...
- Enforced Identity works with authenticated self-signing.
- Enforced identity authentication works with digital and electronic signature fields.
- Enforced authentication does not apply when only a Stamp is used as a signature.
- Embedded signing in an iframe doesn't support Phone or Email OTP authentication when an Enforce identity authentication challenge is enabled. Use a non-embedded signing experience for these agreements.
Streamline your work with Acrobat Sign
Manage and sign documents online quickly and easily.
