This document describes configuration of providers for personal identity document verification and user presence check.
The document verification process is currently supported for following providers:
- ZenID - use value
zenid
in configuration - Mock - useful for simple testing and local runs - use value
mock
in configuration
The authorization of all API calls is secured by an API key value. It has to be sent as the Authorization: api_key VALUE
header value.
Check the bottom of the Manual/Configuration
page for more details.
The API key value can be configured/get from the Access
page configuration:
- Role to be granted:
ApiFull
- Condition:
ApiKeyEqualsValue
- Value: the value here is the value of the API key
It is recommended to create a custom validation profile. The sensitivity of selected validators can be tuned-up or disabled completely at the Sensitivity
page.
The profile can be then set as the default or specified in the configuration properties.
When calling document-verification/init-sdk
following implementation fields are used:
- Init token - send a token value
sdk-init-token
in the request bodyattributes
map field - SDK response - receive the value under
zenid-sdk-init-response
from the responseattributes
map field
The document verification process is currently supported for following providers:
- iProov - use value
iproov
in configuration - Mock - useful for simple testing and local runs - use value
mock
in configuration
There are a few needed configuration changes to bring a successful integration. All the following configuration tuning has to be requested from the iProov's support team on a per-service basis:
- presence check image
- an accepted person image from finished and successful presence check process
- requires enabling of the
frame
response feature for /api/v2/claim/verify/validate
- failure reason
- a more detailed description of the presence check failure
- requires enabling of the
reason
response feature for /api/v2/claim/verify/validate