PingOne

Configuring PingOne Verify

Configure and integrate PingOne Verify into your user identity verification flow.

Before you begin

Regardless of the configuration method you choose, you’ll need:

About this task

There are four ways to configure PingOne Verify:

  • API integration

  • PingOne DaVinci

  • PingFederate Integration Kit

  • Mobile SDK

The configuration method that you choose depends on your role.

Role Configuration Method

Admins and developers

Typically use the PingOne REST API or PingOne DaVinci to get started quickly and test a verify transaction.

PingFederate admins

Use the PingFederate admin console to configure the PingOne Verify Integration Kit.

PingFederate supplies the authentication policy and user verification status for PingOne Verify.

Mobile developers

Use the PingOne Verify mobile SDK (iOS or Android) to create the app your users employ for ID verification.

  • PingOne API

  • PingOne DaVinci

  • PingFederate

  • Mobile SDK

Using the PingOne REST API

About this task

To configure PingOne Verify with the PingOne REST API:

Steps

  1. Create your theme in PingOne Branding and themes to brand the PingOne Verify web experience for your end users.

  2. (Optional) Use language localization to configure one or more languages and modify the PingOne Verify text fields that are presented to end users.

  3. Optional: If you enabled one-time passcode (OTP) through phone or email verification in your policy, create notification templates.

  4. Trigger your first Verify transaction:

    1. Read Getting started with the PingOne APIs.

    2. Download the PingOne Postman collection.

    3. Note the variables you must value.

    4. Obtain a PingOne access token.

      Your {{authPath}} environment variable in Postman should begin with auth.pingone. See PingOne API domains to determine the correct {{authPath}} for your region. Note that nothing trails the domain in the {{authPath}} variable.

    5. Create a new Verify transaction with the Create Verify Transaction API call.

      Your \{{apiPath}} environment variable in Postman should begin with api.pingone. See PingOne API domains to determine the correct \{{apiPath}} for your region. Note that the trailing /v1 is required (for example, api.pingone.com/v1).

      For more information, see PingOne API requests.

      Result:

      Postman renders a QR code.

      A screen capture of the QR code that Postman renders when creating a Verify transaction.

    6. Scan the QR code with a smartphone camera to try the mobile web flow.

  5. View the data submitted in the transaction and the scores returned from verification services.

    Choose from:

    • Using the API: Use the Verified Data and Meta Data endpoints.

    • Using the PingOne admin console:

      1. In PingOne, go to Environment → Audit.

      2. Edit the Time Range and Within fields as needed.

      3. For Filter Type, select Event Type.

      4. For Filter, enter verify in the Search Filter Type field.

      5. Select any of the Verify event types.

        For more information, see Event types.

        A screen capture of the PingOne Audit page with

      6. Click Run.

      7. To view the specific data and scores from an event, click View in the Details column in the report summary.

Using PingOne DaVinci

Before you begin

Add PingOne DaVinci to your PingOne environment. For more information, see Creating an environment.

About this task

To configure PingOne Verify using PingOne DaVinci:

Steps

  1. Create your theme in PingOne Branding and themes to brand the PingOne Verify web experience for your end users.

  2. (Optional) Use language localization to configure one or more languages and modify the PingOne Verify text fields that are presented to end users.

  3. Optional: If you enabled OTP through phone or email verification in your policy, create notification templates.

  4. Import a flow template in PingOne DaVinci by downloading it from the Integration Directory: PingOne Verify quick start flow template.

  5. Update the flow with your PingOne Verify policy:

    1. Click the PingOne Verify Create transaction node in the flow.

    2. In the Verify Policy list, select the policy to use.

    A screen capture of the PingOne Verify Create transaction node details in PingOne PingOne.

  6. To run the flow and trigger a PingOne Verify transaction, click Try Flow.

    Result:

    PingOne DaVinci renders a QR code.

    A screen capture of the QR code that you can scan with your mobile device to start the verification process.

  7. Scan the QR code on your mobile device to try the mobile web flow.

  8. View the data submitted in the transaction and the scores returned from verification services.

    Choose from:

    • Using the API: Use the Verified Data and Meta Data endpoints.

    • Using the PingOne admin console:

      1. In PingOne, go to Environment → Audit.

      2. Edit the Time Range and Within fields as needed.

      3. For Filter Type, select Event Type.

      4. For Filter, enter verify in the Search Filter Type field.

      5. Select any of the Verify event types.

        For more information, see Event types.

        A screen capture of the PingOne Audit page with

      6. Click Run.

      7. To view the specific data and scores from an event, click View in the Details column in the report summary.

Using PingFederate

About this task

To use PingFederate to configure the PingOne Verify Integration Kit:

Steps

Using the PingOne Verify mobile SDK

About this task

Mobile application developers use the PingOne Verify mobile SDK for iOS and PingOne Verify mobile SDK for Android to create the PingOne Verify app for their users. The app is a self-service app for iOS or Android devices that guides the user through the process of taking photos of their ID and a selfie and submitting the photos to PingOne for verification.

To use the PingOne Verify mobile SDK:

Steps

  1. Run the sample app from Github:

  2. Integrate the PingOne Verify mobile SDK into your own app: