Integrating the CData JDBC Driver for PingOne with Ignition SCADA

Ignition is an industrial supervisory control and data acquisition (SCADA) and industrial Internet of Things (IIoT) platform from Inductive Automation. Its central Gateway service manages device connections, tags, and database connections. Ignition doesn't ship with a connector for PingOne, so reaching PingOne data usually means custom middleware or manual exports.

The CData JDBC Driver for PingOne bridges this gap by exposing PingOne as a standard Java Database Connectivity (JDBC) data source. Ignition treats any JDBC driver as a standard database connection. Once the driver is registered in the Gateway, you can query live PingOne data from the Script Console, SQL Bridge, tags, or a Perspective or Vision screen, without replication, custom connectors, or extract, transform, load (ETL) pipelines.

This guide outlines the steps to install and commission Ignition, register the CData JDBC Driver for PingOne, create the connection, and verify it with a live query.

Prerequisites

• Ignition for Windows (Windows 10/11 or Windows Server), with administrator rights to install a Windows service
• CData JDBC Driver for PingOne
• A PingOne account with valid credentials and application programming interface (API) access enabled
• A supported desktop browser (Google Chrome, Mozilla Firefox, Microsoft Edge, or Safari) to open the Gateway web interface

Step 1: Install and set up Ignition

If Ignition is already installed and running, skip to Step 2.

Download Ignition

1. Go to the Inductive Automation downloads page and download Ignition for Windows.
2. This single download is the full Ignition Gateway installer. It includes both the Gateway service and the Designer Launcher, so you don't need a separate Designer download.

Install Ignition

1. Run the installer, accept the license agreement, and choose an install location.
2. Leave Install as a Windows Service checked so the Gateway starts with Windows.
3. Finish the installer. The Gateway service starts, and a browser window opens to http://localhost:8088 and shows the Commissioning wizard. If the page shows a Browser Not Supported notice, open the same address in Chrome, Firefox, Edge, or Safari.

Commission the Gateway

1. In the Commission Ignition Gateway wizard, set a Gateway Name and create an administrator username and password.
2. Accept the End User License Agreement, then start a trial or activate a purchased Ignition license.
3. When commissioning finishes, log in with the administrator account. You land on the Gateway Home page.

Note: A trial shows a countdown timer on every Gateway page, and the timer resets when the Gateway service restarts. This is fine for testing, but production use requires a license.

Step 2: Register the CData JDBC Driver in Ignition

Ignition lets you upload any third-party JDBC driver through the Gateway web interface, without touching the file system directly.

1. Log in to the Gateway as an administrator.
2. Go to Connections > Databases > Settings, open the Drivers tab, and click Create JDBC Driver.
3. In the dialog, enter the following:
   • Name: PingOne
   • Classname: cdata.jdbc.pingone.PingOneDriver
   • Driver Type: Generic
   • Default Validation Query: SELECT Id FROM [CData].[Administrators].Users LIMIT 1
   
4. Click Create JDBC Driver. In current Ignition 8.3 releases, the create dialog doesn't include a Java archive (JAR) file upload field, so you add the JAR file in the next step.
5. Open the menu at the right of the new driver row, choose Manage JAR files, upload cdata.jdbc.pingone.jar from the lib folder of the driver installation, and save.
6. Confirm the driver shows an INSTALLED status in the drivers list.

Step 3: Create the PingOne connection

1. Go to Connections > Databases > Connections and click Create Database Connection.
2. On the Driver Selection step, select PingOne and click Next.
3. On the Database Setup step, set the Name to PingOne. Leave Username empty and select None for Password, because the credentials go in the connect URL.
4. In Connect URL, enter the connection string:

   jdbc:pingone:AuthScheme=OAuth;WorkerAppEnvironmentId=eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e;Region=NA;OAuthClientId=client_id;OAuthClientSecret=client_secret;InitiateOAuth=GETANDREFRESH;

   
5. Click Create Database Connection and confirm the connection shows a VALID status on the Database Connections page.

Connection properties for 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.

Note: If a password or token contains a semicolon, the connect URL breaks, so reset it to a value without one.

Step 4: Query live PingOne data from Ignition

With the connection valid, you can query live PingOne data from the Designer.

1. Open the Ignition Designer Launcher, select your Gateway (click Add Designer and enter http://localhost:8088 if it isn't listed), and click Open Designer. Log in with the Gateway administrator account.
2. Open or create a project. The Designer opens with the Project Browser, Tag Browser, and Component Palette panels.
3. In the Designer, go to Tools > Script Console. In the Multiline Buffer, enter a test query and click Execute. Replace [CData].[Administrators].Users with any table available in your PingOne connection:

   print system.db.runQuery(
       "SELECT Id, Username FROM [CData].[Administrators].Users LIMIT 10",
       "PingOne")

   
4. A successful query prints PyDataset rows:10 cols:2 in the Interactive Interpreter panel, which confirms Ignition retrieved live data from PingOne through the CData JDBC Driver.

Note: The connection name in the script must match the name you gave the connection in Step 3.

Step 5: Verify the results

1. Print the rows and compare the values with the same records in PingOne:

   ds = system.db.runQuery("SELECT Id, Username FROM [CData].[Administrators].Users LIMIT 10", "PingOne")
   for row in ds:
       print row["Id"], row["Username"]

2. Optionally, run a second query against another table and a filtered query to confirm schema discovery and filtering.
3. Optionally, restart the Gateway service and confirm the connection returns to VALID.

Troubleshooting

Test the driver outside Ignition

To confirm the driver works independently of the Gateway, run this standalone Java example. The cdata.jdbc.pingone.jar and cdata.jdbc.pingone.lic files must be in the same directory and on the classpath.

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;

public class CDataExample {
    public static void main(String[] args) throws Exception {
        Class.forName("cdata.jdbc.pingone.PingOneDriver");
        String connectionString = "jdbc:pingone:AuthScheme=OAuth;WorkerAppEnvironmentId=eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e;Region=NA;OAuthClientId=client_id;OAuthClientSecret=client_secret;InitiateOAuth=GETANDREFRESH;";
        try (Connection conn = DriverManager.getConnection(connectionString)) {
            Statement stmt = conn.createStatement();
            ResultSet rs = stmt.executeQuery("SELECT Id, Username FROM [CData].[Administrators].Users LIMIT 10");
            while (rs.next()) {
                System.out.println(rs.getString("Id") + ", " + rs.getString("Username"));
            }
        }
    }
}

---

Build live, governed PingOne connectivity in Ignition with CData

With the CData JDBC Driver for PingOne registered, your team can query live PingOne data from Ignition without ETL infrastructure, manual exports, or custom integration code, and reuse the same connection in tags, SQL Bridge, and Perspective or Vision screens.

Start your free trial today to see how you can give Ignition live, secure access to hundreds of external systems with CData.