Create Informatica Mappings From/To an ODBC Data Source for PingOne

Informatica provides a powerful, elegant means of transporting and transforming your data. By utilizing the CData ODBC Driver for PingOne, you are gaining access to a driver based on industry-proven standards that integrates seamlessly with Informatica's powerful data transportation and manipulation features. This tutorial shows how to transfer and browse PingOne data in Informatica PowerCenter.

Connect to PingOne as an ODBC Data Source

Information for connecting to PingOne follows, along with different instructions for configuring a DSN in Windows and Linux environments.

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.

Windows

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.

Linux

If you are installing the CData ODBC Driver for PingOne in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData PingOne Source]
Driver = CData ODBC Driver for PingOne
Description = My Description
AuthScheme = OAuth
WorkerAppEnvironmentId = eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e
Region = NA
OAuthClientId = client_id
OAuthClientSecret = client_secret
InitiateOAuth = GETANDREFRESH

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Create a Linked Table to [CData].[Administrators].Users Data

Follow the steps below to create a linked table, which enables you to access live [CData].[Administrators].Users data.

Create the ODBC Connection

Follow the steps below to connect to PingOne in Informatica PowerCenter:

1. In the Informatica Developer tool connect to your repository and create a project.
2. In the Connection Explorer pane, right-click and click Create a Connection.
3. In the New Database Connection wizard that is displayed, enter a name and Id for the connection and in the Type menu select ODBC.
4. In the Connection String property, enter the DSN.

NOTE: If you are working in a Linux operating system, set the Driver Manager for Linux property to unixODBC 2.3.x.

Create the PingOne Data Object

After you have created an ODBC connection to PingOne, you can now access PingOne entities in Informatica. Follow the steps below to add [CData].[Administrators].Users entities to your project.

1. In the Object Explorer, right-click your project and then click New -> Data Object.
2. In the wizard that is displayed, select the Relational Data Object option.
3. Click the Browse button next to the Connection box and select the ODBC connection you created in the previous step.
4. Select the option to create a data object from an existing resource and click the Browse button next to the Resource box.
5. In the dialog that is displayed, clear the Show Default Schema Only option and expand the node for the ODBC connection. Select the entity that you want. 👁 The driver models PingOne entities as relational tables. (Salesforce is shown.)
   

You can now browse the table in the Data Viewer: Right-click the node for the table and then click Open. On the Data Viewer view, click Run.

👁 Table data and metadata in the Data Viewer. (Salesforce is shown.)

Create the Mapping

Follow the steps below to add the PingOne source to a mapping:

1. In the Object Explorer, right-click your project and then click New -> Mapping.
2. Expand the node for the PingOne connection and then drag the data object for the table onto the editor.
3. In the dialog that appears, select the Read option.

👁 The source PingOne table in the mapping. (Salesforce is shown.)

Follow the steps below to map PingOne columns to a flat file:

1. In the Object Explorer, right-click your project and then click New -> Data Object.
2. Select Flat File Data Object -> Create as Empty -> Fixed Width.
3. In the properties for the PingOne object, select the rows you want, right-click, and then click copy. Paste the rows into the flat file properties.
4. Drag the flat file data object onto the mapping. In the dialog that appears, select the Write option.
5. Click and drag to connect columns.

To transfer PingOne data, right-click in the workspace and then click Run Mapping.

👁 The completed mapping. (Salesforce is shown.)