Integrate PingOne Data in Your Informatica Cloud Instance

Informatica Cloud allows you to perform extract, transform, and load (ETL) tasks in the cloud. With the Cloud Secure Agent and the CData JDBC Driver for PingOne, you get live access to PingOne data, directly within Informatica Cloud. In this article, we will walk through downloading and registering the Cloud Secure Agent, connecting to PingOne through the JDBC Driver and generating a mapping that can be used in any Informatica Cloud process.

Informatica Cloud Secure Agent

To work with the PingOne data through the JDBC Driver, install the Cloud Secure Agent.

1. Navigate to the Administrator page in Informatica Cloud 👁 Image
   
2. Select the Runtime Environments tab
3. Click "Download Secure Agent" 👁 Image
   
4. Make note of the Install Token 👁 Image
   
5. Run the installer on the client machine and register the Cloud Secure Agent with your username and install token 👁 Image
   

NOTE: It may take some time for all of the Cloud Secure Agent services to get up and running.

Connecting to the PingOne JDBC Driver

With the Cloud Secure Agent installed and running, you are ready to connect to PingOne through the JDBC Driver.

Adding the JDBC Driver to the Secure Agent Machine

1. Navigate to the following directory on the Secure Agent machine:

   %Secure Agent installation directory%/ext/connectors/thirdparty/

2. Create a folder and add the driver JAR file (cdata.jdbc.pingone.jar) based on the type of mapping that you want to configure.

   For mappings, create the following folder and add the driver JAR file:

   informatica.jdbc_v2/common

   For mappings in advanced mode, also create the following folder and add the driver JAR file:

   informatica.jdbc_v2/spark

3. Restart the Secure Agent.

Connecting to PingOne in Informatica Cloud

After installing the driver JAR file, you are ready to configure your connection to PingOne in Informatica Cloud. Start by clicking the Connections tab and clicking New Connection. Fill in the following properties for the connection:

• Connection Name: Name your connection (i.e.: CData PingOne Connection)
• Type: Select "JDBC_V2"
• Runtime Environment: Select the runtime environment where you installed the Secure Agent
• JDBC Driver Class Name: The name of the JDBC driver class: cdata.jdbc.pingone.PingOneDriver
• JDBC Connection URL: Set this to the JDBC URL for PingOne. Your URL will look similar to the following:
  
  

  jdbc:pingone: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:

  • : 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.

  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.

  👁 Using the built-in connection string designer to generate a JDBC URL (Google Sheets is shown.)
  
• Username: Set this to a placeholder value (since PingOne does not require a username)
• Password: Set this to a placeholder value (since PingOne does not require a password)

👁 Configuring the Connection (Google Sheets is shown.

Create a Mapping for PingOne Data

With the connection to PingOne configured, we can now access PingOne data in any Informatica process. The steps below walk through creating a mapping for PingOne to another data target.

1. Navigate to the Data Integration page 👁 Image
   
2. Click New.. and select Mapping from the Mappings tab 👁 Image
   
3. Click the Source Object and in the Source tab, select the Connection and set the Source Type 👁 Selecting the Source Connection and Source Type
   
4. Click "Select" to choose the table to map 👁 Selecting the Source Object
   
5. In the Fields tab, select the fields from the PingOne table to map 👁 Selecting Source Fields to map
   
6. Click the Target object and configure the Target source, table and fields. In the Field Mapping tab, map the source fields to the target fields. 👁 Selecting the Target Field Mappings
   

With the mapping configured, you are ready to start integrating live PingOne data with any of the supported connections in Informatica Cloud. Download a free, 30-day trial of the CData JDBC Driver for PingOne and start working with your live PingOne data in Informatica Cloud today.