Identity proofing is a method of collecting identity documents and identity attributes to verify whether a person is who they claim to be.
Enterprises thrive to secure their services and users which is critical for them. Typically creating a trusted user database is the first step of security measures by avoiding dummy or fake accounts when users self-register. Trusted user access to service is less prone to a security breach.
Identity proofing online at user signup or new registration to system will ensure the identity is who they claim to be. As part of new user registration to the system, the workflow will collect evidence such as valid supporting documents for validation and gather user attributes for identity verification. This process will ensure that the user is legitimate. Besides, identity can be used to check the fraud databases to ensure identity does not pose a risk to be a part of the system.
Identity proofing at authentication also secures login for users but gives different user experience and few users might feel it is cumbersome to access the system.
NetIQ SSPR product offers a new user registration self-service workflow. This article will show how to add Identity proofing offered by Jumio.
Step1: Deploy SSPR as alone or along with Access Manager
Step2: Enable a New User registration profile with SSPR configuration.
Step 3: Disable user after registration is successful as a post-registration event
Step 4: Redirect the user to a custom URL to initiate identity proofing online service.
For more help please visit SSPR documentation: https://www.netiq.com/documentation/self-service-password-reset-42/sspr-adminguide/data/bookinfo.html
Step 1: Create an endpoint for SSPR to redirect the user to initiate the additional workflow.
Step 2: Endpoint calls the Jumio service rest endpoint to get user redirection URL with an access token.
Step3: Create endpoint URL for handling success, failure responses from Jumio service
Step 4: Create REST endpoint as call back URL where Jumio service will post the user document validation and user attribute verification information offline to browser transaction.
Step 5. Based on Jumio’s result posted to call back endpoint enable or don’t enable the user in user repository. Additionally, one can store the information sent from Jumio service to new or existing attributes for further reference or investigation.
Step 1: Register for service
Step 2: create API credentials
Login to portal -> settings -> API Credentials -> Transaction Creation APIs
Step 3: Configure application settings
Login to portal -> settings -> Application settings -> General
Minimal configuration recommended: Callback URL, Success URL, Error URL, Select Capture method.
Note: Please do contact Jumio’s support or documentation for any help.
The below video is the demo of Identity proofing with the SSPR's New User Registration flow using Jumio’s identity proofing online service.