Build PingOne Visualizations in Tableau Cloud

Tableau Cloud is an analytics platform fully hosted in the cloud. When paired with CData Connect AI, you get instant, cloud-to-cloud access to PingOne data for visualizations, dashboards, and more. This article shows how to connect to PingOne and build visualizations from PingOne data in Tableau Cloud.

CData Connect AI provides a pure cloud-to-cloud interface for PingOne, allowing you to easily build visualizations from live PingOne data in Tableau Cloud without installing connectors or publishing worksheets and data sources from Tableau Desktop. As you build visualizations, Tableau Cloud generates SQL queries to gather data. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc) directly to PingOne, leveraging server-side processing to quickly return PingOne data.

Configure PingOne Connectivity for Tableau Cloud

To work with PingOne data from Tableau Cloud, we need to connect to PingOne from Connect AI, provide user access to the connection, and create a Workspace for the PingOne data.

Connect to PingOne from Connect AI

CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "PingOne" from the Add Connection panel

3. Enter the necessary authentication properties to connect to PingOne.

   To connect to PingOne, configure these properties:

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

   Configuring WorkerAppEnvironmentId

   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 WorkerAppEnvironmentId to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   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 AuthScheme to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • InitiateOAuth: GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the OAuthAccessToken each time you connect, use InitiateOAuth.
   • OAuthClientId: The Client ID you obtained when you created your custom OAuth application.
   • OAuthClientSecret: The Client Secret you obtained when you created your custom OAuth application.
   • CallbackURL: 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 OAuthSettingsLocation, 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.

   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add PingOne Connection page and update the User-based permissions.

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Configure PingOne Endpoints for Tableau Cloud

After connecting to PingOne, create a workspace for your desired table(s).

1. Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace).
2. Click Add to add new assets to the Workspace.
3. Select the PingOne connection (e.g. PingOne1) and click Next.
4. Select the table(s) you wish to work with and click Confirm.
5. Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}

With the connection, PAT, and Workspace configured, you are ready to connect to PingOne data from Tableau Cloud.

Visualize Live PingOne Data in Tableau Cloud

The steps below outline creating a new data source in Tableau Cloud based on the virtual PingOne database in Connect AI and building a simple visualization from the data.

1. Log into Tableau Cloud, select a account, and create a new workbook.
2. In the new workbook, choose the OData Connector from the data wizard and fill in the values for your Connect AI instance.
   • Set Server to the OData URL for your Workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}
   • Set Authentication to Username and Password
   • Set Username to your Connect AI username (e.g. [email protected])
   • Set Password to a PAT for the above user
   
3. Select your newly created database and the table(s) you wish to visualize (defining relationships for JOINad tables as needed).

4. Select Dimensions and Measures and configure your visualization.

Real-Time Access to PingOne Data from Cloud Applications

At this point, you have a direct, cloud-to-cloud connection to live PingOne data from your Tableau Cloud workbook. You can create new visualizations, build dashboards, and more, with no need to publish data sources and workbooks from Tableau Desktop. For more information on gaining live access to data from more than 100 SaaS, Big Data, and NoSQL sources from cloud applications like Tableau Cloud, refer to our Connect AI page.