We are proud to share our inclusion in the 2024 Gartner Magic Quadrant for Data Integration Tools. We believe this recognition reflects the differentiated business outcomes CData delivers to our customers.
Get the Report →Access Live PingOne Data in Coginiti Pro
Connect to and query live PingOne data from the GUI in the Coginiti Pro: SQL Analytics Tool.
Coginiti Pro is a single tool for all your SQL data and analytics needs, designed specifically for data engineers, analysts, and data scientists. When paired with the CData JDBC Driver for PingOne, Coginiti Pro can access and query live PingOne data. This article describes how to connect to and query PingOne data from Coginiti Pro.
With built-in optimized data processing, the CData JDBC Driver for PingOne offers unmatched performance for interacting with live PingOne data. When you issue complex SQL queries to PingOne, the driver pushes supported SQL operations, like filters and aggregations, directly to PingOne and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). In addition, its built-in dynamic metadata querying allows you to work with and analyze PingOne data using native data types.
Gather Connection Properties and Build a Connection String
Download the CData JDBC Driver for PingOne installer, unzip the package, and run the JAR file to install the driver. Then gather the required connection properties.
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:
- From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
- 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.
- In the environment's home page navigation sidebar, click Applications.
- Find your OAuth or Worker application details in the list.
-
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:
- The driver obtains an access token from PingOne and uses it to request data.
- 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.
NOTE: To use the JDBC driver in Coginiti Pro, you may need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.
Built-in Connection String Designer
For assistance constructing the JDBC URL, use the connection string designer built into the PingOne JDBC Driver. Double-click the JAR file or execute the jar file from the command line.
java -jar cdata.jdbc.pingone.jar
Fill in the connection properties (including the RTK) and copy the connection string to the clipboard.
Create a JDBC Data Source for PingOne Data
- Open Coginiti Pro and in the File menu, select "Edit Drivers."
- In the newly opened wizard, click "Add" and select "Generic."
In the "JDBC Drivers" wizard, set the driver properties (below) and click "Create Driver."
- Set JDBC Driver Name to a useful name, like CData JDBC Driver for PingOne.
- Click "Add Files" to add the JAR file from the "lib" folder in the installation directory (e.g. cdata.jdbc.pingone.jar)
- Select the Class Name: cdata.jdbc.pingone.PingOneDriver.
Create a Connection using the CData JDBC Driver for PingOne
- In the File menu, click "Edit Connections."
- In the newly opened wizard, click "Add" and select "Generic."
- In the "Connections" wizard, set the connection properties.
- Set Connection name to an identifying name.
- Set Database JDBC driver to the Driver you configured earlier.
- Set JDBC URL to the JDBC URL configured using the built-in connection string designer (e.g. jdbc:pingone:AuthScheme=OAuth;WorkerAppEnvironmentId=eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e;Region=NA;OAuthClientId=client_id;OAuthClientSecret=client_secret;InitiateOAuth=GETANDREFRESH
- Click "Test" to ensure the connection is configured properly. Click "Save."
Query PingOne Using SQL
- Open the Connections tab by clicking on database icon: .
- Click the plus sign () to add a new query tab.
Once the query console is open, write the SQL script you wish to execute and click "Run at Cursor".
NOTE: You can use the explorer on the left to determine table/view names and column names.
Using the explorer
- In the "Select connection" field, select the connection you wish to query.
- Expand your newly created connection, expand the "CData" catalog, and expand the PingOne catalog.
- Expand "Tables" or "Views" to find the entity you wish to query.
- Expand your selected entity to explore the fields (columns).
Free Trial & More Information
Download a free, 30-day trial of the CData JDBC Driver for PingOne and start working with your live PingOne data in Coginiti Pro. Reach out to our Support Team if you have any questions.