Connect to PingOne Data from Crystal Reports

Crystal Reports is a business intelligence application by SAP designed to help you analyze your data with well-formatted, pixel-perfect, and multi-page reports. When paired with CData Connect AI, Crystal Reports gets access to live PingOne data. This article demonstrates how to connect to PingOne using Connect AI and report on PingOne data in Crystal Reports.

CData Connect AI provides a pure SQL Server interface for PingOne, allowing you to query data from PingOne without replicating the data to a natively supported database. 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 return the requested PingOne data quickly.

Configure PingOne Connectivity for Crystal Reports

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

Connect to PingOne from Crystal Reports using Connect AI

To establish a connection from Crystal Reports to CData Connect AI, you will need to download the JDBC driver.

1. Open the Client Tools page of CData Connect AI.
2. Search for and select JDBC.
3. Download and run the setup file.
4. When the installation is complete, locate the JDBC Connect JAR file in the JDBC driver's installation directory, for example, C:\Program Files\CData\JDBC Driver for CData Connect\lib.
5. Copy the JDBC Connect JAR file (cdata.jdbc.connect.jar).

After copying the JDBC CData Connect JAR file, you will need to paste it into the Crystal Reports installation location and configure the connection to Connect AI.

1. Find the installation directory for Crystal Reports, for example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib
2. Paste the JDBC Connect JAR file into the Crystal Reports installation directory.
3. Go to the parent java folder. For example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java This folder should contain a CRConfig file.
4. Open CRConfig in a text editor.
5. Add the path to the JDBC CData Connect JAR file in the of the CRConfig file, for example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib
6. Log into Crystal Reports and start a blank report.
7. In the Database Expert dialog, click Create New Connection.
8. Select the JDBC data source and the tables you want to add. Click OK.
9. In the Connection dialog, enter the Connection URL (e.g. jdbc:connect:AuthScheme=Basic;user=username;password=PAT;) and Database Classname (e.g. cdata.jdbc.connect.ConnectDriver).
10. Click Finish. The Database Expert dialog displays all available connections.

You can now create reports with the connected data.

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Crystal Reports, try CData Connect AI today!