Re-Authentication

This article explains everything you need to know about QoreID re-authentication

Re-authentication enables QoreID customers to confirm a person's identity again after they have already been verified previously. This can be done for various reasons, such as to ensure that the person is still authorized to access certain information or to prevent unauthorized access.

Re-authentication is enabled by Liveness detection.

Liveness detection is a type of biometric authentication that verifies a person's identity by verifying that they are physically present and not just using a static image or video of them. This is typically done by requiring the person to perform some action, such as blinking or moving their head, demonstrating that they are alive and not a static image.

QoreID Re-authentication

QoreID re-authentication is a process that involves using liveness detection to confirm a person's identity and authenticate their access to an application.

How to use QoreID Re-authentication

:one: Create a Workflow with a digital ID service and Liveness

Create a parent workflow that includes a digital ID service and a liveness check against the digital ID service. Users can only perform re-authentication after they have previously performed a liveness check on QoreID. This is to ensure that the user trying to perform the reauthentication has a valid account that can be used as the basis for the re-authentication

:two: Create a Child Workflow with Re-authentication

Re-authentication can only be added in a child workflow due to its dependency on the user having previously completed a liveness check using QoreID.

:three: Integrate

After creating workflows as stated above, you can go ahead and integrate the QoreID workflows that have been created