Analyze PingOne Data in Cognos Analytics

Cognos Analytics, powered by IBM Watson®, empowers users to cleanse and establish connections with their data while creating visualizations. When integrated with CData Connect AI, users gain immediate, real-time connectivity between cloud-based data sources and Cognos Analytics, facilitating data management, visualization, analytics, and more. This article provides step-by-step guidance on connecting to PingOne via CData Connect AI and subsequently analyzing PingOne data within Cognos Analytics.

NOTE: These instructions require Cognos Analytics 11.2.4 or higher

CData Connect AI offers a dedicated cloud-to-cloud interface for PingOne, enabling users to perform real-time analysis on PingOne data within Cognos without the need to replicate data to a natively supported database. Equipped with built-in optimized data processing capabilities, CData Connect AI efficiently directs all supported SQL operations, including filters and JOINs, directly to PingOne. This harnesses server-side processing to promptly provide the requested PingOne data.

Configure PingOne Connectivity for Cognos Analytics

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

Connect to PingOne from Cognos Analytics

The steps below outline connecting to CData Connect AI from Cognos Analytics to analyze live PingOne data.

Download and install the CData Connect AI JDBC driver

1. Open the Integrations page of CData Connect AI.
2. Search for and select JDBC.
3. Download and run the setup file.
4. When the installation is complete, copy the JAR file (cdata.jdbc.connect.jar) from the installation directory (e.g., C:\Program Files\CData\JDBC Driver for CData Connect\lib) to the "drivers" folder in your Cognos Analytics installation directory.

Configure the Connection to CData Connect AI

1. Open IBM Cognos and navigate to Manage > Data server connections.
2. Click the icon to add a data server.
3. Select CData Connect AI.
4. Set JDBC URL to the appropriate connection string. For example:

   
       jdbc:connect:AuthScheme=Basic;user=username;password=PAT;
     

5. Set Driver class name to "cdata.jdbc.connect.ConnectDriver"
6. Create and store authenticate credentials by selecting an authentication method
   • Set Username to your CData Connect AI username (e.g., [email protected])
   • Set Password to the PAT you previously generated.
7. Click Test connection to confirm that the connection succeeds.

At this point, you are ready to analyze and visualize PingOne data in Cognos Analytics. For more information about using Cognos Analytics, please refer to the Cognos Analytics documentation.

Live Access to PingOne Data for Analytics

Now you have a direct, cloud-to-cloud connection to live PingOne data from Cognos Analytics. You can create new visualizations, build reports, and more — 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.