#
Generic OpenID Connect Integration with VerifEye
This guide walks you through setting up VerifEye as a generic OpenID Connect (OIDC) provider, enabling you to use VerifEye's biometric verification as an authentication factor in any OIDC-compliant identity provider or application.
#
Prerequisites
Before configuring your identity provider, ensure you have:
- A VerifEye account and API key
- Admin access to your identity provider or application
- Understanding of the OpenID Connect flow
- A verification configuration set up for OIDC integration (see below)
#
Configuring the VerifEye Verification
To integrate VerifEye with any OIDC-compliant system, you need to create a VerifEye verification configuration that will be used as the OIDC provider. Follow these steps:
You can create a new verification configuration in the VerifEye Developer Console under Verification Configurations. Make sure to note the configuration ID and API key, as you will need these for the identity provider setup.
#
1. Basic Settings
When creating the verification configuration, set the following basic settings:
#
2. Verifier Configuration
For the OIDC integration, you must configure the verification configuration to include the following settings:
- Face Recognition
- Unique Match Verification: one person can be only registered once in the system, if the same person tries to register again with a different identifier (email address), the verification will fail
- Match Verification: one person can be registered multiple times in the system, if the same person tries to register again with a different identifier (email address), the verification will pass
Additionally you can configure other settings such as liveness detection, age or gender verification.
#
3. Advanced Settings
For the OIDC integration, you must also configure the following advanced settings:
- Include Signature: enabled
- Include Verification Result: enabled
- Include Custom Input Parameters: enabled
- Force Signed Input: enabled
#
OIDC Provider Configuration Details
When configuring VerifEye as an OpenID Connect provider in your identity provider or application, use the following values:
#
Required Configuration Values
#
Regional Endpoints
Configure the OpenID Connect endpoints based on your VerifEye region:
#
EU Region
#
US Region
#
Authentication Flow
The VerifEye OIDC service follows the standard OAuth 2.0/OpenID Connect authorization code flow:
- User attempts to authenticate with your application
- Application redirects user to VerifEye authorization endpoint
- User completes biometric verification using your configured verification settings
- Upon successful verification, user is redirected back to your application with authorization code
- Your application exchanges the authorization code for access and ID tokens
- User authentication is complete