Access Live PingOne Data in SAS JMP via ODBC

You can use the CData ODBC Driver for PingOne to integrate live data into your statistical analysis with SAS JMP. The driver proxies your queries directly to the PingOne API, ensuring that your analysis reflects any changes to the data. The CData ODBC Driver supports the standard SQL used by JMP in the background as you design reports.

This article shows how to access PingOne data into a report and create data visualization. It also shows how to use SQL to query PingOne data from the JMP Query Builder.

Access PingOne Data as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

To connect to PingOne, configure these properties:

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

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

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

Desktop Applications

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

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

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Import PingOne Data with the Query Builder

After you have created the PingOne DSN, you can use SQL to invoke the capabilities of the PingOne API. Follow the steps below to execute some supported queries in the Query Builder:

1. In SAS JMP, click File -> Database -> Query Builder. The Select Database Connection dialog is displayed.
2. Click New Connection.
3. On the Machine Data Source tab, select the ODBC DSN you configured and then click Next. 👁 Select the ODBC DSN you configured. (Salesforce is shown.)
   
4. The Select Tables for Query dialog is displayed and in the Available Tables section, select a table and click Primary. After choosing the primary table, click Build Query to open the Query Builder. 👁 Select the Primary table for the Query. (Salesforce is shown.)
   
5. As you drag Available Columns to the Included Columns tab, the underlying SQL query is updated and you can view the generated SQL Query in the SQL tab. 👁 The generated query in the Query Builder. (Salesforce is shown.)
   
6. Click Run Query to display the data. 👁 The results of a query in the Query Builder. (Salesforce is shown.)
   
7. To refresh the results with the current data, right-click Update from Database and click Run Script.

Visualize PingOne Data

After importing, you can use the Graph Builder to create graphs visually. To open the Graph Builder, click the Graph Builder button in the toolbar.

1. Drag a dimension column onto the x axis. For example, Id.
2. Drag a measure column onto the y axis. For example, Username.
3. Select a chart type. For example, a bar chart. 👁 Configuration of a basic chart. (Salesforce is shown.)