Automate PingOne Integration Tasks from PowerShell

The CData Cmdlets for PingOne are standard PowerShell cmdlets that make it easy to accomplish data cleansing, normalization, backup, and other integration tasks by enabling real-time access to PingOne.

PowerShell Cmdlets or ADO.NET Provider?

The Cmdlets are not only a PowerShell interface to PingOne, but also an SQL interface; this tutorial shows how to use both to retrieve PingOne data. We also show examples of the ADO.NET equivalent, which is possible with the CData ADO.NET Provider for PingOne. To access PingOne data from other .NET applications, like LINQPad, use the CData ADO.NET Provider for PingOne.

Once you have acquired the necessary connection properties, accessing PingOne data in PowerShell can be enabled in three steps.

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.

PowerShell

1. Install the module:

   Install-Module PingOneCmdlets

2. Connect:

   $pingone = Connect-PingOne -AuthScheme "$AuthScheme" -WorkerAppEnvironmentId "$WorkerAppEnvironmentId" -Region "$Region" -OAuthClientId "$OAuthClientId" -OAuthClientSecret "$OAuthClientSecret" -InitiateOAuth "$InitiateOAuth"
   

3. Search for and retrieve data:

   $employeetype = "Contractor"
   $[cdata].[administrators].users = Select-PingOne -Connection $pingone -Table "[CData].[Administrators].Users" -Where "EmployeeType = `'$EmployeeType`'"
   $[cdata].[administrators].users
   

   You can also use the Invoke-PingOne cmdlet to execute SQL commands:

   $[cdata].[administrators].users = Invoke-PingOne -Connection $pingone -Query 'SELECT * FROM [CData].[Administrators].Users WHERE EmployeeType = @EmployeeType' -Params @{'@EmployeeType'='Contractor'}
   

ADO.NET

1. Load the provider's assembly:

   [Reflection.Assembly]::LoadFile("C:\Program Files\CData\CData ADO.NET Provider for PingOne\lib\System.Data.CData.PingOne.dll")
    

2. Connect to PingOne:

    
   $conn= New-Object System.Data.CData.PingOne.PingOneConnection("AuthScheme=OAuth;WorkerAppEnvironmentId=eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e;Region=NA;OAuthClientId=client_id;OAuthClientSecret=client_secret;InitiateOAuth=GETANDREFRESH;")
   $conn.Open()
   

3. Instantiate the PingOneDataAdapter, execute an SQL query, and output the results:

   $sql="SELECT Id, Username from [CData].[Administrators].Users"
   
   $da= New-Object System.Data.CData.PingOne.PingOneDataAdapter($sql, $conn)
   $dt= New-Object System.Data.DataTable
   $da.Fill($dt)
   
   $dt.Rows | foreach {
   	Write-Host $_.id $_.username
   }
    

CodeProject