Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect PingOne Data to Claris FileMaker via ESS using an ODBC Driver and the CData SQL Gateway
Connect to your PingOne data using the ESS feature of Claris FileMaker with MySQL ODBC driver and CData SQL Gateway.
Claris FileMaker is a low-code platform that enables users to quickly create custom apps to manage and automate data workflows. Using the CData ODBC Driver for PingOne and the CData SQL Gateway, FileMaker connects to PingOne data through its ESS (External SQL Source) feature, allowing you to work with PingOne records as if they were native FileMaker tables.
In this article, we configure and use the CData ODBC Driver for PingOne and the CData SQL Gateway, along with the MySQL ODBC Driver, to connect to PingOne data using the ESS functionality in FileMaker.
Create an ODBC Data Source for PingOne
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
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.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
Configuring the CData SQL Gateway
The CData SQL Gateway bridges non-SQL data sources (like SaaS applications, APIs, and NoSQL databases) with SQL-based tools (like FileMaker, MySQL clients, and BI tools).
In simple terms, it exposes any CData driver-supported source - for example, PingOne - as a standard MySQL or SQL Server endpoint.
See the SQL Gateway Overview to set up PingOne data connectivity as a virtual MySQL database. Set up a MySQL remoting service that listens for MySQL requests from clients, and configure the service through the SQL Gateway UI (as shown below). Save the user credentials (Username and Password) for future use.


Once you establish the connection, you can use the CData SQL Gateway to access PingOne data through the MySQL protocol.
Installing the MySQL ODBC Driver
Follow the steps below to install and configure the MySQL ODBC Driver:
- Download and install the latest 64-bit Windows version of the MySQL ODBC Unicode Driver from this link.
- Launch ODBC Data Sources (64-bit) from Windows search. Open the System DSN tab, click Add, select MySQL ODBC Unicode Driver from the Create New Data Source window, and click Finish.
- Enter the following connection details in the MySQL Connector/ODBC Data Source Configuration window:
- Data Source Name: Enter a DSN of your choice
- TCP/IP Server: localhost
- Port: Enter the port set in the SQL Gateway (for this procedure, use "3307")
- User: Enter the username set in the CData SQL Gateway
- Password: Enter the password set in the CData SQL Gateway
- Database: CData PingOne Sys
- Click Test to verify that the "Connection Successful" dialog box appears. Then click OK to save the configuration details.

You have now successfully configured the MySQL ODBC Driver.
Use FileMaker ESS function to load PingOne data
In this section, we explore how to use the ESS (External SQL Source) feature to retrieve data in the FileMaker application. Follow the given steps to complete the process:
- Open FileMaker Pro. Navigate to Create from the left panel and select Blank > Create.
- Enter a desired filename and click Save.
- In Manage Database, remove the Tables and Fields from the respective tabs. Select the Relationships tab and click Add Table.
- In Specify Table, expand the Data Source dropdown menu and select Add ODBC Data Source. Click OK.
- In Select ODBC Data Source, select the previously configured MySQL ODBC driver and click Continue.
- In the Edit Data Source window, enter the following details:
- Name: This field will be auto-filled. Enter a new name of choice if necessary.
- Type: Select "ODBC".
- Under Authentication, select the Specify username and password radio button and enter the following details:
- User name: Enter the username set in the CData SQL Gateway.
- Password: Enter the password set in the CData SQL Gateway.
- Catalog Name: CData PingOne Sys
- Click OK.
- View the tables from PingOne populated under the Data Source section. Select the table of your choice and click OK.
- The Relationships tab now displays the selected table and its metadata. Click OK.
- Select the table from the Layout dropdown. The PingOne table data appears on the screen. (As shown)








Get Started Today
Download a free 30-day trial of CData ODBC Driver for PingOne to integrate PingOne data into Claris FileMaker and use PingOne data in your FileMaker applications.
Contact our Support Team if you have any questions.