Create PingOne-Connected Enterprise Applications in OutSystems

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Use CData Connect AI to connect to PingOne Data from OutSystems and build custom enterprise apps using live PingOne data.

OutSystems is a low-code platform which provides the tools for companies to developer, deploy, and manage omnichannel enterprise applications. When paired with CData Connect AI, you get instant, cloud-to-cloud access to PingOne data for business applications. This article shows how to create a virtual database for PingOne in Connect AI and build a simple app from PingOne data in OutSystems.

The CData Connect AI provides a pure cloud-to-cloud interface for PingOne, allowing you to build reports from live PingOne data in OutSystems — without replicating the data to a natively supported database. As you create applications to work with data, OutSystems generates SQL queries to gather data. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to PingOne, leveraging server-side processing to quickly return the requested PingOne data.

Configure PingOne Connectivity for OutSystems

Connectivity to PingOne from OutSystems is made possible through CData Connect AI. To work with PingOne data from OutSystems, we start by creating and configuring a PingOne connection.

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Adding a Connection
  3. Select "PingOne" from the Add Connection panel
  4. Selecting a data source
  5. 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:

    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.

    Configuring a connection (Salesforce is shown)
  6. Click Save & Test
  7. Navigate to the Permissions tab in the Add PingOne Connection page and update the User-based permissions. Updating 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.

  1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the PAT a name and click Create. Creating a new PAT
  4. 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 OutSystems.

Connect to PingOne from OutSystems

The steps below outline connecting to CData Connect AI from OutSystems to create a new PingOne database connection.

  1. Open OutSystems Service Studio
  2. Click the gear icon to open Environment Management in the Service Center Opening the Service Center
  3. Click Administration and select "Database Connections"
  4. Click "New Database Connection"
  5. Configure the database connection:
    • Name: name the connection (e.g. CData Connect AI PingOne)
    • DBMS: SQL Server / Azure SQL
    • Username: a Connect AI user (e.g. [email protected])
    • Password: the PAT for the Connect AI user
    • Server: tds.cdata.com,14333
    • Schema: the name of your PingOne connection (e.g. PingOne1)
    Connecting to the Connect AI
  6. Click "Test Connection"
  7. Click "Create"

Map PingOne Tables or Views to Entities in an Extension Module

Once you create the database connection for PingOne, you can create an extension that maps the tables or views to OutSystems entities. If you have not already done so, create an Application in Service Studio.

  1. Open the Service Studio and open the existing Application
  2. Click "Add Module," set the "Module Name" (e.g. pingone_db_extension), set "Module Type" to "Extension," and click "Create Module" Creating a new extension module
  3. In Integration Studio, connect to your environment
  4. Right-click "Entities" in the extension tree and select "Connect to External Table or View..." Connecting to external tables or views
  5. Follow the steps in the wizard, selecting the tables and views you wish to work with
  6. In the Integration Studio, click "1-Click Publish"
  7. In the "1-Click Publish" wizard, click "Configure" when the process completes
    • In the Service Center, associate the logical database name of the extension to the database connection that the extension will use and click "Apply" Configuring the external extension
  8. In your application, click "Manage Dependencies..."
  9. Add a dependency to the Extension and select the Entities that you will use in your application Adding a dependency to the extension

At this point, you can access and work with PingOne data just like you would with the standard OutSystems entities.

Get CData Connect AI

With Connect AI and OutSystems, you can easily build PingOne-connected applications. Request a free trial of Connect AI and start working with PingOne data in OutSystems today.

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial