Build PingOne-Connected ETL Processes in Google Data Fusion



Load the CData JDBC Driver into Google Data Fusion and create ETL processes with access live PingOne data.

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for PingOne enables users to access live PingOne data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping PingOne data to any data source natively supported in Google Data Fusion, this article walks through piping data from PingOne to Google BigQuery,

Upload the CData JDBC Driver for PingOne to Google Data Fusion

Upload the CData JDBC Driver for PingOne to your Google Data Fusion instance to work with live PingOne data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatapingone-2020.jar

  1. Open your Google Data Fusion instance
  2. Click the to add an entity and upload a driver
  3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
  4. On the "Driver configuration" tab:
    • Name: Create a name for the driver (cdata.jdbc.pingone) and make note of the name
    • Class name: Set the JDBC class name: (cdata.jdbc.pingone.PingOneDriver)
  5. Click "Finish"

Connect to PingOne Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live PingOne data in Google Data Fusion Pipelines.

  1. Navigate to the Pipeline Studio to create a new Pipeline
  2. From the "Source" options, click "Database" to add a source for the JDBC Driver
  3. Click "Properties" on the Database source to edit the properties

    NOTE: To use the JDBC Driver in Google Data Fusion, you will 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.

    • Set the Label
    • Set Reference Name to a value for any future references (i.e.: cdata-pingone)
    • Set Plugin Type to "jdbc"
    • Set Connection String to the JDBC URL for PingOne. For example:

      jdbc:pingone:RTK=5246...;AuthScheme=OAuth;WorkerAppEnvironmentId=eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e;Region=NA;OAuthClientId=client_id;OAuthClientSecret=client_secret;InitiateOAuth=GETANDREFRESH;

      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.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the PingOne JDBC Driver. Either 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 and copy the connection string to the clipboard.

    • Set Import Query to a SQL query that will extract the data you want from PingOne, i.e.:
      SELECT * FROM [CData].[Administrators].Users
  4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
  5. Click "Properties" on the BigQuery sink to edit the properties
    • Set the Label
    • Set Reference Name to a value like pingone-bigquery
    • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
    • Set Dataset to a specific Google BigQuery dataset
    • Set Table to the name of the table you wish to insert PingOne data into

With the Source and Sink configured, you are ready to pipe PingOne data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from PingOne and import it into Google BigQuery.

While this is a simple pipeline, you can create more complex PingOne pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for PingOne and start working with your live PingOne data in Google Data Fusion today.

Ready to get started?

Download a free trial of the PingOne Driver to get started:

 Download Now

Learn more:

PingOne Icon PingOne JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with PingOne.