Authentication

Authentication compares a newly-uploaded Selfie and Facemap to an existing Facemap that is already associated with the account to verify that the current end user is the same person as the known identity.

For a detailed description see Authentication Workflow.

Authentication requires your integration to use either the Web Client or one of the Mobile SDKs A new Facemap is required, which cannot be uploaded through the REST APIs.

Dependencies

  • An existing Facemap must already be associated with the account.

    If your data retention policies remove existing credentials you have the option of using Authentication On-Premises.

  • The Liveness check must pass before the workflow can proceed to Authentication.

Supported Credentials

Decision Details Labels

Decision Type

Label

Description

NOT_EXECUTED

PRECONDITION_NOT_FULFILLED

Required data from another capability is not available.

NOT_EXECUTED

TECHNICAL_ERROR

A technical error prevented the capability from executing.

PASSED

OK

The end user is the same person who previously uploaded credentials under the same account.

REJECTED

FAILED

The end user is not the same person who previously uploaded credentials under the same account.

Data

Key

Type

Description

type

string

The service that is used. Possible values:

  • IPROOV_STANDARD

  • IPROOV_PREMIUM

  • JUMIO_STANDARD
The Authentication capability also returns an additional "validFaceMapForAuthentication" value, which is the href to the facemap used for comparison.