Visualize Live PingOne Data in the Power BI Service

Power BI transforms your company's data into rich visuals for you to collect and organize so you can focus on what matters to you. When paired with CData Connect AI, you get instant access to PingOne data for visualizations, dashboards, and more. This article shows how to build and publish a dataset from PingOne data in Power BI and then create reports on PingOne data in the Power BI service.

CData Connect AI provides a pure SQL interface for PingOne, allowing you to easily build reports from live PingOne data in Power BI — with no need to replicate the data. As you build visualizations, Power BI 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.

NOTE: You can also import PingOne data into Power BI through Connect AI (instead of using the on-premise gateway). Read how in the related Knowledge Base article.

Configure PingOne Connectivity for Power BI

Connectivity to PingOne from Power BI is made possible through CData Connect AI. To work with PingOne data from Power BI, we start by creating and configuring a PingOne connection.

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.

With the connection configured and a PAT generated, you are ready to connect to PingOne data from Power BI.

Connecting to Connect AI from Power BI

To connect to and visualize live PingOne data in the Power BI service, install the on-premise data gateway, add a data source to the gateway from the Power BI service, and publish a dataset from Power BI Desktop to the service.

Install the On-Premises Data Gateway

The Microsoft on-premise data gateway provides secure data transfer between connected data sources and various cloud-based Microsoft tools and platforms. You can read more about the gateway in the Microsoft documentation.

You can download and install the gateway from the Power BI service:

1. Log in to PowerBI.com.
2. Click the Download menu and click Data Gateway.
3. Follow the instructions for installation, making note of the name of the gateway.

Add PingOne as a Data Source to the Power BI Service

Once you have installed the data gateway, you add Connect AI as a data source to the Power BI service:

1. Log in to PowerBI.com.
2. Click the Settings menu and click "Manage gateways."
3. Click "ADD DATA SOURCE" and configure the connection to Connect AI:
   
   
   • Set Data Source Name to something like ConnectCloudPingOne.
   • Choose SQL Server as the Data Source Type.
   • Set Server to tds.cdata.com,14333.
   • Set Database to the name of your PingOne connection (e.g. PingOne1).
   • Set Authentication Method to Basic.
   • Set Username to a Connect AI user (e.g. [email protected])
   • Set Password to the PAT for the user above.

Publish a Dataset from Power BI Desktop

With the gateway installed and Connect AI added as a datasource to the Power BI service, you can publish a dataset from Power BI Desktop to the service.

1. Open Power BI, click Get Data -> More, then select SQL Server database, and click Connect.

2. Set the connection properties and click OK.
   • Set Server to tds.cdata.com,14333.
   • Set Database to the name of your PingOne connection (e.g. PingOne1).
   • Set Data Connectivity mode to DirectQuery*.
   * DirectQuery enables live query processing and real-time visualizations of PingOne data.
3. In the authentication wizard, select Database, set the User name and Password properties, and click Connect.

4. Select the table(s) to visualize in the Navigator dialog.
5. In the Query Editor, you can customize your dataset by filtering, sorting, and summarizing PingOne columns. Click Edit to open the query editor. Right-click a raw to filter the rows. Right-click a column header to perform options like the following:
   • Change column data types
   • Remove a column
   • Group by columns

   Power BI detects each column's data type from the PingOne metadata reported by Connect AI.

   Power BI records your modifications to the query in the Applied Steps section, adjusting the underlying data retrieval query that is executed to the remote PingOne data. When you click Close and Apply, Power BI executes the data Retrieval query.

   Otherwise, click Load to pull the data into Power BI.

6. Define any relationships between the selected entities on the Relationships tab.
7. Click Publish (from the Home menu) and select a Workspace.

Build Reports and Dashboards on PingOne Data in the Power BI Service

Now that you have published a dataset to the Power BI service, you can create new reports and dashboards based on the published data:

1. Log in to PowerBI.com.
2. Click Workspaces and select a workspace.
3. Click Create and select Report.
4. Select the published dataset for the report.
5. Choose fields and visualizations to add to your report.

Live Access to PingOne Data from Cloud Applications

Now you have a direct connection to live PingOne data from the Power BI service. You can create more data sources and new visualizations, build reports, and more — all without replicating PingOne data.

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, sign up for a free trial of CData Connect AI.