Wultra implementation of the enrollment server. The enrollment server publishes the following services:
- PowerAuth Standard RESTful API
- Push Registration API
- Mobile Token Operations API
- Endpoints for Automated Testing
The document verification process is currently supported for following providers:
- ZenID
- Mock - useful for simple testing and local runs
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-tokenin the request bodyattributesmap field - SDK response - receive the value under
zenid-sdk-init-responsefrom the responseattributesmap field
The document verification process is currently supported for following providers:
- iProov
- Mock - useful for simple testing and local runs
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
frameresponse feature for /api/v2/claim/verify/validate
- failure reason
- a more detailed description of the presence check failure
- requires enabling of the
reasonresponse feature for /api/v2/claim/verify/validate