Create Dashboards and Visualize Live PingOne Data in Geckoboard

Geckoboard is a business intelligence tool that simplifies the visualization of key performance indicators (KPIs) by creating live dashboards. It allows teams to consolidate data from various sources - such as Salesforce, Snowflake, Google Analytics, and spreadsheets - and display it in a visually engaging and easy-to-understand format. Designed for simplicity and clarity, Geckoboard helps businesses monitor performance, track goals, and make data-driven decisions.

When used with CData Connect AI, you gain instant, cloud-to-cloud access to PingOne data from Geckoboard for dashboards, monitoring, visualizations, and more. This article explains how to connect to PingOne and create visualizations using PingOne data in Geckoboard.

CData Connect AI offers a seamless SQL Server, cloud-to-cloud interface for PingOne, enabling you to effortlessly create dashboards and visualizations using live PingOne data in Geckoboard. While building visualizations, Geckoboard requires SQL queries to retrieve the necessary data. With built-in optimized data processing, CData Connect AI pushes all supported SQL operations (such as filters and JOINs) directly to PingOne, utilizing server-side processing for fast and efficient data retrieval of PingOne data.

Configure PingOne connectivity for Geckoboard

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

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "PingOne" from the Add Connection panel

3. 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.

   
4. Click Save & Test
5. 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.

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.
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 Geckoboard.

Connect live PingOne data in Geckoboard

Follow these steps to establish a connection from Geckoboard to the CData Connect AI Virtual SQL Server API.

1. Log into Geckoboard
2. Add a custom dashboard name and click Add widget
3. Search for "Databases" in the Connect your data search bar
4. Select SQL Server as the Database type
5. Fill in the connection details:
   • Connection name: enter a name for the connection to CData Connect AI
   • Host: enter the Virtual SQL Server endpoint: tds.cdata.com
   • Port: : enter 14333
   • Database name: enter the Connection Name of the CData Connect AI data source you want to connect to (for example, PingOne1)
   • Username: enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected]
   • Password: enter the PAT you generated on the Settings page
   
6. Click Connect

After successfully configuring your connection, you can query and visualize your PingOne data.

Visualize live PingOne data in Geckoboard

To visualize live PingOne data in Geckoboard, follow these steps:

1. Write an SQL query to select the specific PingOne data needed for visualization in Paste your SQL query compiler screen

Depending on your use case, you can also generate the desired SQL query using the Playground or Query Builder features of CData Connect AI


2. Choose the visualization type (Line Chart, Bar Chart, or Column Chart) that best suits your business requirements
3. The selected chart will be displayed on Geckoboard
4. Click the menu (three dots in the top-right corner of the graph) and select Edit to modify the SQL query or set a refresh interval for the chart

Live access to PingOne data from cloud applications

At this stage, you have established a direct, cloud-to-cloud connection to live PingOne data in Geckoboard. This enables you to create dashboards to monitor and visualize your data seamlessly.

For more details on accessing live data from over 100 SaaS, Big Data, and NoSQL sources through cloud applications like Geckoboard, visit our Connect AI page.