PingOne

Configuring and setting up PingOne Verify

To seamlessly integrate PingOne Verify into your identity workflows, first optionally configure language localization for your end users, then choose your orchestration method.

Configuring PingOne Verify language localization

Optionally use language localization to configure one or more languages and modify the PingOne Verify text fields that are presented to end users in notifications and agreements.

Language localization detects the user’s browser locale and refers to the corresponding language pack in PingOne.

Integrating PingOne language packs provides seamless localization and translation of PingOne Verify user interfaces, allowing users to interact with it in their preferred language. Learn more in Languages.

Steps

  1. In the PingOne admin console, go to User Experience > Languages.

  2. Click your preferred language or add a language. Learn more in Adding a language.

  3. In the Module list, select Identity Verification.

  4. In the Page list, select a page to view the associated keys. The Identity Verification module includes the following pages:

    • Device

    • Document

    • Error Messages

    • General

    • ID Capture

    • Retry

    • Selfie

    • Voice

    Identity Verification module showing pages.

  5. (Optional) In the Compare to: list, select another language to compare the text with a language other than the default language.

  6. In the translation column, click the Pencil icon ().

  7. Edit the text in the translation field to your preferred translation.

  8. Click Save.

  9. In the upper right, click the toggle to enable the language.

Learn more in Downloading a language bundle and Uploading a language bundle.

Configuring and orchestrating PingOne Verify

Seamlessly integrate PingOne Verify into your identity workflows.

Before you begin

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

Metro map of configuring and orchestrating PingOne Verify.

The metro map shows:

  1. The PingOne Verify service is enabled within the PingOne environment.

  2. The default PingOne Verify policy is customized with specific rules and transaction requirements, such as Facial Comparison and Liveness.

  3. Verification transactions are orchestrated using integrated identity options.

  4. The verification flow is executed with the end user, and the results are retrieved.

  5. Oversight is maintained by reviewing results and dashboards.

Steps

  1. Choose one of the following methods to orchestrate a verify transaction:

    Choose from:

    PingOne Advanced Identity Cloud and PingAM

    Integrating with PingOne Advanced Identity Cloud and PingAM

    Advanced Identity Cloud is a digital identity and access management (IAM) software as a service (SaaS) solution for any identity, workforce, or consumer.

    PingAM software manages access to resources, such as web pages, applications, or web services available over a network. PingAM centralizes access control by handling both authentication and authorization.

    To take advantage of PingOne Verify features, you can integrate PingOne Verify nodes into your Advanced Identity Cloud and PingAM journeys. Learn more in Journeys.

    Before you begin

    Make sure you have:

    Steps

    1. Configure the PingOne service in Advanced Identity Cloud.

    2. Set up your user journey in Advanced Identity Cloud or PingAM with PingOne Verify nodes in the journey:

    3. Validate that the PingOne Verify Evaluation node is working by doing the following:

      1. Configure the node with Store Verification Metadata and Store Verified Data enabled.

      2. Use a Scripted Decision node to return the node state and make sure the values of the pingOneVerifyMetadata, pingOneVerifyVerifiedData, and pingOneVerifyEvaluationFailureReason properties are what you expect. You can also run the journey with Debugging enabled.

      3. Add message nodes attached to individual results outputs to understand the flow.

    4. Validate that the PingOne Verify Completion Decision node is working by doing the following:

      1. Use logger messages in your Completion processing script to determine the processing goals and outcomes, and monitor the log.

      2. Evaluate the nodeState values of the PingOne Verify nodes that were set in the script using a Scripted Decision node that returns the nodeState, or with the Debugger enabled

      3. Add message nodes attached to individual results outputs to understand the flow.

    PingFederate

    Using PingFederate

    To use PingFederate to configure the PingOne Verify Integration Kit:

    Steps

    PingOne API

    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 Variables you must value in the PingOne API documentation to determine the correct {{authPath}} for your geography. 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 Variables you must value in the PingOne API documentation to determine the correct {{apiPath}} for your geography. Note that the trailing /v1 is required (for example, api.pingone.com/v1).

        Learn more in 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 Verification Metadata 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.

          You can find a complete list of events logged in PingOne in Audit Reporting Events in the PingOne API documentation.
          A screen capture of the PingOne Audit page with 'verify' entered in the Filter field.

        6. Click Run.

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

    PingOne DaVinci

    To configure PingOne Verify using PingOne DaVinci:

    Before you begin

    Add PingOne DaVinci to your PingOne environment. Learn more in Creating an environment.

    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 the PingOne Verify quick start flow template in PingOne DaVinci by downloading it from the Ping Identity Marketplace.

    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 DaVinci.

    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.

      include::partial$p1_verify_scan_qr_code]

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

      Choose from:

      • Using the API: Use the Verified Data and Verification Metadata 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.

          You can find a complete list of events logged in PingOne in Audit Reporting Events in the PingOne API documentation.
          A screen capture of the PingOne Audit page with 'verify' entered in the Filter field.

        6. Click Run.

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

    Mobile SDK

    Using the PingOne Verify mobile SDK

    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:

  2. Review results and dashboards in Reviewing and managing verification and Monitoring PingOne Verify transaction activity and license usage.