Analyze PingOne Data in Infragistics Reveal

Reveal is a data visualization solution provided by Infragistics and can be paired with the CData API Server to build dynamic dashboards from live PingOne data. The CData API Server generates an OData API for PingOne, which is natively consumable in Reveal. In this article, we walk through connecting to PingOne in API Server and connecting to the API Server from Infragistics Reveal to create a simple dashboard.

Connect to PingOne from API Server

CData API Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.

1. Open API Server and click Settings -> Connection -> Add Connection 👁 Adding a connection
   
2. Select "PingOne" 👁 Selecting a Connector (Salesforce is shown).
   
3. Enter the necessary authentication properties to connect to PingOne.

   To connect to PingOne, configure these properties:

   • : The region where the data for your PingOne organization is being hosted.
   • : The type of authentication to use when connecting to PingOne.
   • Either (required when using the default PingOne domain) or , configured as described below.

   Configuring WorkerAppEnvironmentId

   is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

   First, find the value for this property:

   1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
   2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
   3. In the environment's home page navigation sidebar, click Applications.
   4. Find your OAuth or Worker application details in the list.
   5. Copy the value in the Environment ID field. It should look similar to:
      

      WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

   Now set to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

   Authenticating to PingOne with OAuth

   PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

   • Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
   • To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
   • Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

   OAuth (Authorization Code grant)

   Set to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • : GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the each time you connect, use .
   • : The Client ID you obtained when you created your custom OAuth application.
   • : The Client Secret you obtained when you created your custom OAuth application.
   • : The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

   When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

   1. The driver obtains an access token from PingOne and uses it to request data.
   2. The OAuth values are saved in the location specified in , to be persisted across connections.

   The driver refreshes the access token automatically when it expires.

   For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

   👁 Configuring a connection (Salesforce is shown).
   

Add PingOne Resource Definitions in API Server

After connecting to PingOne, create Resources, which represent API endpoints for PingOne data.

1. Click Settings -> Resources -> Add Resource 👁 Adding a new resource
   
2. Select the PingOne connection 👁 Selecting a connection (Salesforce is shown)
   
3. Select the table you wish to retrieve and click Next 👁 Selecting a Table (Salesforce is shown)
   
4. (Optional) Edit the resource to select specific fields and more
5. Save the settings

Add an API Server User

Create a User to connect to PingOne from Reveal through API Server.

1. Click Settings -> Users
2. Click Add
3. Configure a User with access to the PingOne Connection and Resource(s) 👁 Creating a new user
   

(Optional) Configure Cross-Origin Resource Sharing (CORS)

When accessing and connecting to multiple different domains from an application such as Ajax, there is a possibility of violating the limitations of cross-site scripting. In that case, configure the CORS settings in Settings -> Server.

• Enable cross-origin resource sharing (CORS): ON
• Allow all domains without '*': ON
• Access-Control-Allow-Methods: GET, PUT, POST, OPTIONS
• Access-Control-Allow-Headers: Authorization

Save the changes to the settings.

Create a Dashboard in Reveal

With the API Server configured, we can visualize PingOne data in Reveal.

1. Log into Reveal and click Dashboards -> New 👁 Adding a new dashboard
   
2. Click Data Source -> OData Feed 👁 Adding a new OData data source
   
3. Specify the API Server API endpoint URL, for example: https://serverurl/api.rsc 👁 Configuring the OData URL
   
4. Select Generic Credentials and specify the API Server username and authentication token 👁 Configuring the credentials
   
5. Select the entity you wish to visualize 👁 Selecting an entity to visualize (Salesforce is shown.)
   
6. Select fields and choose a chart type 👁 Visualizing data in Reveal (Salesforce is shown.)
   

More Information & Free Trial

At this point, you have created a simple dashboard from live PingOne data. For more information on creating OData feeds from PingOne (and more than 150 other sources), visit the API Server page. Download a free, 30-day trial and start working live PingOne data in tools that consume OData APIs.