Connect to and Visualize Live PingOne Data in Tableau Prep

Tableau is a visual analytics platform transforming the way businesses use data to solve problems. When paired with the CData Tableau Connector for PingOne, you can easily get access to live PingOne data within Tableau Prep. This article shows how to connect to PingOne in Tableau Prep and build a simple chart.

The CData Tableau Connectors enable high-speed access to live PingOne data in Tableau. Once you install the connector, you simply authenticate with PingOne and you can immediately start building responsive, dynamic visualizations and dashboards. By surfacing PingOne data using native Tableau data types and handling complex filters, aggregations, & other operations automatically, CData Tableau Connectors grant seamless access to PingOne data.

NOTE: The CData Tableau Connectors support Tableau Prep Builder 2020.4.1 or higher. If you are using an older version of Tableau Prep Builder, you will need to use the CData JDBC Driver.

Install the CData Tableau Connector

When you install the CData Tableau Connector for PingOne, the installer should copy the TACO and JAR files to the appropriate directories. If your data source does not appear in the connection steps below, you will need to copy two files:

1. Copy the TACO file (cdata.pingone.taco) found in the lib folder of the connector's installation location (C:\Program Files\CData\CData Tableau Connector for PingOne 20XX\lib on Windows) to the Tableau Prep Builder repository:
   • Windows: C:\Users\[Windows User]\Documents\My Tableau Prep Repository\Connectors
   • MacOS: /Users//Documents/My Tableau Prep Repository/Connectors
2. Copy the JAR file (cdata.tableau.pingone.jar) found in the same lib folder to the Tableau drivers directory, typically [Tableau installation location]\Drivers.

Connect to PingOne in Tableau Prep Builder

Open Tableau Prep Builder and click "Connect to Data" and search for "PingOne by CData." Configure the connection and click "Sign In."

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 the Connector (Sage Intacct is shown)

Discover and Prep Data

Drag the tables and views you wish to work with onto the canvas. You can include multiple tables.

👁 Selecting table(s)

Data Cleansing & Filtering

To further prepare the data, you can implement filters, remove duplicates, modify columns and more.

1. Start by clicking on the plus next to your table and selecting the Clean Step option. 👁 Adding a Clean Step
   
2. Select the field values to filter by. As you select values, you can see how your selections impact other fields. 👁 Selecting test entries (Sage Intacct is shown).
   
3. Opt to "Keep Only" or "Exclude" entries with your select values and the data changes in response. 👁 Excluding selected entries (Sage Intacct is shown).
   

Data Joins and Unions

Data joining involves combining data from two or more related tables based on a common field or key.

1. To join multiple tables, drag a related table next to an existing table in the canvas and place it in the Join box. 👁 Joining two tables (Sage Intacct is shown).
   
2. Select the foreign keys that exist in both tables. 👁 Setting the joining fields/columns (Sage Intacct is shown).
   

Exporting Prepped Data

After you perform any cleansing, filtering, transformations, and joins, you can export the data for visualization in Tableau.

1. Add any other needed transformations then insert an Output node at the end of the flow.
2. Configure the node to save to a file in the format of your choice. 👁 Saving the results (Sage Intacct is shown).
   

Once the output data is saved, you can work with it in Tableau, just like you would any other file source.

Using the CData Tableau Connector for PingOne with Tableau Prep Builder, you can easily join, cleanse, filter, and aggregate PingOne data for visualizations and reports in Tableau. Download a free, 30-day trial and get started today.