PingOne Recognize

Integration flows

Introduction

Learn how the PingOne Recognize Web SDK components can be integrated into a web application and backend server, to enable biometric authentication.

Integration overview

Live enrollment flow

To authenticate with PingOne Recognize, a user must first enroll their biometric template.

PingOne Recognize enrollment registers the user’s biometric features in a privacy-preserving manner using a variety of methods supported by the Web SDK.

Authentication flow

The most common authentication scenarios for the PingOne Recognize Web SDK are:

  • access to a web application

  • authorization as a second factor

Authentication in a web application

In this scenario, the user is using a web app to access a resource that requires strong authentication. Because the web app uses the PingOne Recognize Web SDK to connect to the PingOne Recognize Authentication Service, the user authenticates successfully once they pass liveness and recognition checks.

PingOne Recognize web components

PingOne Recognize Web is composed of two main elements:

  • PingOne Recognize Web SDK

  • PingOne Recognize Authentication Service

PingOne Recognize Web SDK

The PingOne Recognize Web SDK supports all baseline browsers, and exposes API methods to interact with the PingOne Recognize Privacy-Preserving Network to perform the following actions:

  • Enroll a user

  • Authenticate

PingOne Recognize authentication service

The PingOne Recognize SaaS backend offers APIs which can be used to perform specific operations through backend-to-backend calls. For example, you can enroll users individually or in bulk using selfies captured by other services. To learn more, refer to IDV Bridge SaaS.