Build PingOne-Connected Apps in Choreo
The Choreo platform from WS02 is a versatile platform designed for low-code and cloud-native engineering. Developers, even those without advanced coding skills, can leverage Choreo's user-friendly low-code environment to simplify application development. When combined with CData Connect AI, users gain immediate cloud-to-cloud access to PingOne data for applications. This article details the process of connecting to PingOne using Connect AI and building an application with real-time access to PingOne data within Choreo.
CData Connect AI delivers a pure cloud-to-cloud interface for PingOne, enabling you to construct applications within Choreo that utilize live PingOne data data, all without the need for data replication to a natively supported database. With its built-in optimized data processing capabilities, CData Connect AI efficiently directs all supported SQL operations, including filters and JOINs, directly to PingOne, capitalizing on server-side processing to swiftly provide the requested PingOne data.
Configure PingOne Connectivity for Choreo
Connectivity to PingOne from Choreo is made possible through CData Connect AI. To work with PingOne data from Choreo, we start by creating and configuring a PingOne connection.
- Log into Connect AI, click Sources, and then click Add Connection
- Select "PingOne" from the Add Connection panel
-
Enter the necessary authentication properties to connect to PingOne.
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:
- From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
- 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.
- In the environment's home page navigation sidebar, click Applications.
- Find your OAuth or Worker application details in the list.
-
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:
- The driver obtains an access token from PingOne and uses it to request data.
- 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.
- Click Save & Test
-
Navigate to the Permissions tab in the Add PingOne Connection page and update the User-based permissions.
Add a Personal Access Token
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
- Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
- On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
With the connection configured and a PAT generated, you are ready to connect to PingOne data from Choreo.
Connect to PingOne from Choreo
The steps below outline connecting to CData Connect AI from Choreo to create a new application with access to live PingOne data.
Creating a Construct
-
Sign in to the Choreo platform. Note: This article is from the perspective of an Anonymous user.
-
Select Components from the left sidebar and then click +Create. Next, choose Manual Trigger and then Start from scratch.
-
Give the manual trigger a Name and Description and click Create.
-
After the trigger is created, click on Edit Code.
-
The Ballerina Low-Code IDE is displayed. Choreo automatically generates a construct in the low-code diagram
view. Delete this construct by highlighting it and clicking on the trashcan icon.
-
Click the + icon towards the top of the screen and select Main from the Add Constructs
toolbar on the right. In the following Function Configuration form, click Save.
Adding the CData Connect AI Connector
- Click the + icon between the Start and End ellipses and click Connector.
- In the Connectors sidebar on the right, search for "CData". Click CData Connect to open the Connector settings pane.
-
In the Connector settings pane, enter the configuration settings:
- Enter an Endpoint Name for your use. In this example, we use "connectEndpoint".
- In the User field, enter the email address of the CData Connect AI user, wrapped in quotation marks (for example, "[email protected]").
- In the Password field, enter the PAT you generated earlier, wrapped in quotation marks (for example, "SampleToken").
- After clicking Save, the low-code editor appears with the CData Connect AI logo.
Adding a Query Action
- Click the + icon between the new and end shapes, select Action, and then select our existing connector endpoint.
- Select query for the connector Operation. There is now an Action pane on the right.
- Enter a SQL query to retrieve PingOne data as the sqlQuery parameter for the query. For example:
SELECT * FROM PingOne1.PingOne.[CData].[Administrators].Users LIMIT 10- When writing the query, be sure to specify the Connection Name as the catalog and Data Source Name as the schema. For example, PingOne1.PingOne.
- These parameters appear on the Connections page of your CData Connect AI dashboard.
Iterating over PingOne Data
- Click the Show Source icon in the top right of the code editor.
- Add an import statment to import the ballerina/io library:
import ballerina/io;
- Next, add a from statement after the query action to iterate through the results of the SQL query:
- The code for the construct will now look similar to this:
- Click Save to save the action. The diagram should now look similar to this:
check from record{} result in resultStream
do {
io:println("Full [CData].[Administrators].Users details: ", result);
};
import ballerinax/cdata.connect;
import ballerinax/cdata.connect.driver as _;
import ballerina/io;
public function main() returns error? {
connect:Client connectEp = check new (user = "connect_cloud_username", password="connect_cloud_pat");
stream<record {}, error=""?> resultStream =
connectEp->query(sqlQuery = `SELECT * FROM PingOne1.PingOne.[CData].[Administrators].Users LIMIT 10`);
check from record{} result in resultStream
do {
io:println("Full [CData].[Administrators].Users details: ", result);
};
}
Deploying the Program
Once you have added all of your desired actions to your program, follow these steps:
- Commit and push your final source code in the web editor and sync those changes with the Choreo platform.
- Click Deploy in the left navigation bar of the Choreo Console.
- Under Build Area, click Configure & Deploy to deploy your program.
- When prompted, enter the same CData Connect AI username and password that you used earlier and click Deploy.
You have now created an application with access to live PingOne data in Choreo.
Get CData Connect AI
For more information about using Choreo with CData Connect AI, see the CData Connect Ballerina Guide. To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!