Create Reports from PingOne Data in Looker Studio

Looker Studio, formerly known as Google Data Studio, empowers users to craft customized reports featuring data visualizations that can be shared with clients while reflecting your brand identity. When combined with CData Connect AI, you gain immediate cloud-to-cloud access to PingOne data to create visualizations, dashboards, and more. This article provides step-by-step instructions on establishing a virtual database for PingOne and generating reports from PingOne data within Looker Studio.

CData Connect AI offers a seamless cloud-to-cloud interface tailored for PingOne, making it straightforward to construct reports directly from live PingOne data within Looker Studio without the need for data replication. As you create visualizations, Looker Studio generates queries to retrieve data. With its inherent optimized data processing capabilities, CData Connect AI efficiently channels all supported query operations, including filters, JOINs, and more, directly to PingOne. This leverages server-side processing to swiftly provide the requested PingOne data.

Configure PingOne Connectivity for Looker Studio

Connectivity to PingOne from Looker Studio is made possible through CData Connect AI. To work with PingOne data from Looker Studio, 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.

With the connection configured, you are ready to connect to PingOne data from Looker Studio.

Visualize Live PingOne Data from Looker Studio

The steps below outline connecting to CData Connect AI from Looker Studio to create a new PingOne data source and build a simple visualization from the data.

1. Log into Looker Studio, click data sources, create a new data source, and choose CData Connect AI Connector.

2. Click Authorize and allow access to your Google account.
3. Click Authorize to authenticate with your CData Connect AI instance
4. In the CData Connect AI Connector in Looker Studio select Connections to import from the dropdown and click Next

5. Now select a Connection (e.g. PingOne1) and click Next
6. Select a Table (e.g. [CData].[Administrators].Users) or use a Custom Query and click Connect to continue
7. If needed, modify columns, click Create Report, and add the data source to the report.

8. Select a visualization style and add it to the report.
9. Select Dimensions and Measures to customize your visualization.

Live Access to PingOne Data from Cloud Applications

Now you have a direct, cloud-to-cloud connection to live PingOne data from your Looker Studio workbook. You can create more data sources and new visualizations, build reports, and more — all without replicating PingOne data.

Try CData Connect AI and get real-time data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications.