Create PingOne Dataflows on PowerBI.com

The CData Power BI Connector for PingOne seamlessly integrates with the tools and wizards in Power BI, including the real-time data workflows on PowerBI.com. Follow the steps below to pull data directly into DataFlows on PowerBI.com and use the Power BI Gateway to configure automatic refresh.

Create a DSN

Installing the Power BI Connector creates a DSN (data source name) called CData Power BI PingOne. This the name of the DSN that Power BI uses to request a connection to the data source. Configure the DSN by filling in the required connection properties.

You can use the Microsoft ODBC Data Source Administrator to create a new DSN or configure (and rename) an existing DSN: From the Start menu, enter "ODBC Data Sources." Ensure that you run the version of the ODBC Administrator that corresponds to the bitness of your Power BI Desktop installation (32-bit or 64-bit).

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.

Pulling PingOne Data Directly Into Your Dataflow

With the data source configured, follow the steps below to load data from PingOne tables into your DataFlow.

Set Up the Power BI Gateway

Follow the steps below to configure the gateway on your machine:

1. Run the CData Power BI Connector installer. If you have not already done so, download the Power BI Gateway.
2. Select the on-premises data gateway (recommended) option.
3. Sign into the gateway.
4. Name the gateway and specify a recovery key.

5. In the Connectors step, choose a folder where the gateway will look for the CData Power BI Connector. This article uses C:\Users\PBIEgwService\Documents\Power BI Desktop\Custom Connectors\. Copy the .pqx files for the CData Connector (found in C:\Users\USERNAME\Documents\Power BI Desktop\Custom Connectors\) to the folder you configured.

   NOTE: The account configured for the service (NT SERVICE\PBIEgwService) needs to be able to access the folder chosen for the gateway. If needed, you can change the service account in the Service Settings section of the gateway installer.

6. Confirm that the entry CData.PowerBI.PingOne is displayed in the list in the Connectors section.

Set up Power BI Online for a Dataflow

1. In Power BI Online, create a new workspace, which is also known as an app, if you do not already have one. Note that this is only available with Power BI Pro or higher.
2. Set up your On-Premises Gateway. The steps for this are in the Configuring the Gateway section of this article.
3. Go back to Power BI Online. In settings, go to 'Manage Gateways', and add a new data source to your Gateway
   • Enter the Data Source Name, the name that the data source will be referred to within Power BI Online
   • Select the Data Source Type, (e.g. CData Power BI Connector for PingOne) and set the Data Source Name (e.g. CData Power BI PingOne)
   • Set Authentication Method to "Anonymous"
   • Set Privacy Level as needed
4. Click Add to finish the configuration (do not skip the test connection as it is important to know if a successful connection was made).
   
   If you would like to manage the users that have access to this data source, you can go to the Users tab.

Set up your Dataflow and pull the PingOne data

1. In the new workspace, go to Create > Dataflow > Add New Entities.
2. Choose the ODBC data source and enter the correct connection properties.
   Enter your DSN name in the ODBC connection string section, dsn=CData Power BI PingOne. Choose your gateway and set the authentication type to Anonymous.
3. Choose the table(s) you want to work with and click Transform data.
   If you want to make any changes to the query, you can right click on the query and click on Advanced Editor.

Configure Data Refresh on PowerBI.com

Refresh your dataflow to have the most up to date data.

• To refresh manually, open the dataflow options menu from your workspace -> Dataflows and click Refresh Now.
• To schedule refreshes, open the dataflow options menu from your workspace -> Dataflows and click Schedule Refresh. Enable the option to keep your data up to date. Specify the refresh frequency in the menus.

At this point, you will have a Dataflow built on top of live PingOne data. Learn more about the CData Power BI Connectors for PingOne and download a free trial from the CData Power BI Connector for PingOne page. Let our Support Team know if you have any questions.