PingOne
  • 21 Mar 2025
  • 2 Minutes to read
  • Dark
    Light

PingOne

  • Dark
    Light

Article summary

PingOne is a cloud-based identity as a service (IDaaS) framework for secure identity access management that uses an organization-based model to define tenant accounts and their related entities within the PingOne platform. For detailed information refer to the PingOne’s official documentation.

Integration Method: API

Tables: User Inventory Info (5003)

This integration supports the following event.

Event

Description

Users

List of the Users

This integration supports the following version.

PingOne API version

v1

Note:

PingOne is a continuously updated cloud service. As of this document preparation, latest release was on 19 March 2025.

Prerequisites

  • The user should have access to the PingOne instance.

  • The user should have the environment ID for which user list will be fetched.

  • The user should have a client ID and client secret for an application for that particular environment.

  • The user should have access to the DataBee console.

Configuration Overview

  1. Get the Environment ID, Client Key and Client Secret for Ping One.

  2. Add the PingOne data feed in the DataBee console with the below parameters.

    DataBee Parameter

    Ping One Parameter

    Environment ID

    Environment ID

    Client Key

    Client ID

    Client Secret

    Client Secret

PingOne Configuration

The integration must be configured with an environment ID, and for that environment, a specific application requires a client ID and client secret.

The steps below are for creating an application and obtaining the appropriate roles and permissions to access user data from selected environments.

  1. Login to the portal for the particular environment.

    Note:

    The login page link varies based on the environment ID and region. Use the link provided by your identity team.

    A screenshot of a login form  AI-generated content may be incorrect.

  2. Select Applications > Applications.

  3. Click on + (plus) button beside Applications title, to create a new application.
     

  4. Enter a valid, unique name for the application.

    A screenshot of a computer  AI-generated content may be incorrect.

  5. Select the ‘Application Type’ as Worker and click Save.

    A screenshot of a computer  AI-generated content may be incorrect.

  6. Under Roles tab, Click on Grant Roles button.

    A screenshot of a computer  AI-generated content may be incorrect.

  7. Select Roles > Available responsibilities.

  8. Select the Identity Data Admin role for the environment whose user list you want to access. Click Save.
     

  9. Go to the Overview tab, copy the Environment ID, Client ID, and Client Secret. These details will be used when we create feed in DataBee.

     

  10. Scroll down and expand the Connection Details. Copy the Token Endpoint. This will be used when we create feed in DataBee.



  11. Make sure the application is enabled. If it is disabled, click the Toggle button to enable.

  12. Get TLD(Top Level Domain). This will be used when we create the feed in DataBee. Find the below domain as per region.

DataBee Configuration

  1. Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.

    A screenshot of a computer  AI-generated content may be incorrect.

  2. Search for Ping One and click it as shown below.

  3. Click on the API Ingest option for collection method.

    A screenshot of a computer  AI-generated content may be incorrect.

  4. Enter feed contact information and click Next.

    A screenshot of a computer  AI-generated content may be incorrect.

  5. In the configuration page, confirm the following:

    • Authorization Method: OAuth2

    • API Base URL: this is the base URL that DataBee will interact with.

      • Replace the .com (tld) as per the mentioned TLDs.

    • Client Key: paste the Client ID.

    • Client Secret: paste the Client Secret.

    • Token URL: replace the placeholder Token URL with copied token endpoint.

    • Event Types: preselected for all the event types that integration pulls.

    • Environment ID: paste the Environment ID.

  6. Click Submit.

Troubleshooting Tips

  • If you are facing unauthorized (401) error, this might be possibly due to incorrect Credentials. Please refer Credentials to get client Key and client Secret.


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence