Create Datasets from PingOne in Domo Workbench and Build Visualizations of PingOne Data in Domo

Domo helps you manage, analyze, and share data across your entire organization, enabling decision makers to identify and act on strategic opportunities. Domo Workbench provides a secure, client-side solution for uploading your on-premise data to Domo. The CData ODBC Driver for PingOne links Domo Workbench to operational PingOne data. You can build datasets from PingOne data using standard SQL queries in Workbench and then create real-time visualizations of PingOne data in the Domo service.

The CData ODBC Drivers offer unmatched performance for interacting with live PingOne data in Domo due to optimized data processing built into the driver. When you issue complex SQL queries from Domo to PingOne, the driver pushes supported SQL operations, like filters and aggregations, directly to PingOne and utilizes the embedded SQL Engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze PingOne data using native Domo data types.

Connect to PingOne as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

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.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

After creating a DSN, you will need to create a dataset for PingOne in Domo Workbench using the PingOne DSN and build a visualization in the Domo service based on the dataset.

Build a Dataset for PingOne Data

You can follow the steps below to build a dataset based on a table in PingOne in Domo Workbench using the CData ODBC Driver for PingOne.

1. Open Domo Workbench and, if you have not already, add your Domo service server to Workbench. In the Accounts submenu, click Add New, type in the server address (i.e., domain.domo.com) and click through the wizard to authenticate. 👁 Connecting to the Domo Service.
   
2. In the DataSet Jobs submenu, click Add New.
3. Name the dataset job (i.e., ODBC PingOne [CData].[Administrators].Users), select ODBC Connection Provider as the transport method, and click through the wizard. 👁 Configuring the DataSet Job.
   
4. In the newly created DataSet Job, navigate to Source and click to configure the settings.
5. Select System DSN for the Connection Type.
6. Select the previously configured DSN (CData PingOne Sys) for the System DSN.
7. Click to validate the configuration. 👁 Configuring the Source Settings.
   
8. Below the settings, set the Query to a SQL query:

   SELECT * FROM [CData].[Administrators].Users

   NOTE: By connecting to PingOne data using an ODBC driver, you simply need to know SQL in order to get your data, circumventing the need to know PingOne-specific APIs or protocols.
9. Click preview. 👁 Querying PingOne Data.
   
10. Check over the generated schema, add any transformations, then save and run the dataset job. 👁 Save and Run the Configured DataSet Job (Salesforce is shown).
    

With the dataset job run, the dataset will be accessible from the Domo service, allowing you to build visualizations, reports, and more based on PingOne data.

Create Data Visualizations

With the DataSet Job saved and run in Domo Workbench, we are ready to build visualizations of the PingOne data in the Domo service.

1. Navigate to the Data Center. 👁 Accessing the Data Center (Salesforce is shown).
   
2. In the data warehouse, select the ODBC data source and drill down to our new dataset. 👁 Selecting the PingOne Dataset (Salesforce is shown).
   
3. With the dataset selected, choose to create a visualization.
4. In the new card:
   • Drag a Dimension to the X Value.
   • Drag a Measure to the Y Value.
   • Choose a Visualization.
   👁 Visualizing PingOne Data in Domo (Salesforce is shown).
   

With the CData ODBC Driver for PingOne, you can build custom datasets based on PingOne data using only SQL in Domo Workbench and then build and share visualizations and reports through the Domo service.