Create Datasets from Okta in Domo Workbench and Build Visualizations of Okta Data in Domo

Domo helps you manage, analyze, and share data across your entire organization, enabling decision makers to identify and act on strategic opportunities. Domo Workbench provides a secure, client-side solution for uploading your on-premise data to Domo. The CData ODBC Driver for Okta links Domo Workbench to operational Okta data. You can build datasets from Okta data using standard SQL queries in Workbench and then create real-time visualizations of Okta data in the Domo service.

The CData ODBC Drivers offer unmatched performance for interacting with live Okta data in Domo due to optimized data processing built into the driver. When you issue complex SQL queries from Domo to Okta, the driver pushes supported SQL operations, like filters and aggregations, directly to Okta and utilizes the embedded SQL Engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Okta data using native Domo data types.

Connect to Okta as an ODBC Data Source

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 Okta, set the Domain connection string property to your Okta domain.

You will use OAuth to authenticate with Okta, so you need to create a custom OAuth application.

Creating a Custom OAuth Application

From your Okta account:

1. Sign in to your Okta developer edition organization with your administrator account.
2. In the Admin Console, go to Applications > Applications.
3. Click Create App Integration.
4. For the Sign-in method, select OIDC - OpenID Connect.
5. For Application type, choose Web Application.
6. Enter a name for your custom application.
7. Set the Grant Type to Authorization Code. If you want the token to be automatically refreshed, also check Refresh Token.
8. Set the callback URL:
   • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the property.
   • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
9. In the Assignments section, either select Limit access to selected groups and add a group, or skip group assignment for now.
10. Save the OAuth application.
11. The application's Client Id and Client Secret are displayed on the application's General tab. Record these for future use. You will use the Client Id to set the OAuthClientId and the Client Secret to set the OAuthClientSecret.
12. Check the Assignments tab to confirm that all users who must access the application are assigned to the application.
13. On the Okta API Scopes tab, select the scopes you wish to grant to the OAuth application. These scopes determine the data that the app has permission to read, so a scope for a particular view must be granted for the driver to have permission to query that view. To confirm the scopes required for each view, see the view-specific pages in Data Model < Views in 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.

After creating a DSN, you will need to create a dataset for Okta in Domo Workbench using the Okta DSN and build a visualization in the Domo service based on the dataset.

Build a Dataset for Okta Data

You can follow the steps below to build a dataset based on a table in Okta in Domo Workbench using the CData ODBC Driver for Okta.

1. Open Domo Workbench and, if you have not already, add your Domo service server to Workbench. In the Accounts submenu, click Add New, type in the server address (i.e., domain.domo.com) and click through the wizard to authenticate. 👁 Connecting to the Domo Service.
   
2. In the DataSet Jobs submenu, click Add New.
3. Name the dataset job (i.e., ODBC Okta Users), select ODBC Connection Provider as the transport method, and click through the wizard. 👁 Configuring the DataSet Job.
   
4. In the newly created DataSet Job, navigate to Source and click to configure the settings.
5. Select System DSN for the Connection Type.
6. Select the previously configured DSN (CData Okta Sys) for the System DSN.
7. Click to validate the configuration. 👁 Configuring the Source Settings.
   
8. Below the settings, set the Query to a SQL query:

   SELECT * FROM Users

   NOTE: By connecting to Okta data using an ODBC driver, you simply need to know SQL in order to get your data, circumventing the need to know Okta-specific APIs or protocols.
9. Click preview. 👁 Querying Okta Data.
   
10. Check over the generated schema, add any transformations, then save and run the dataset job. 👁 Save and Run the Configured DataSet Job (Salesforce is shown).
    

With the dataset job run, the dataset will be accessible from the Domo service, allowing you to build visualizations, reports, and more based on Okta data.

Create Data Visualizations

With the DataSet Job saved and run in Domo Workbench, we are ready to build visualizations of the Okta data in the Domo service.

1. Navigate to the Data Center. 👁 Accessing the Data Center (Salesforce is shown).
   
2. In the data warehouse, select the ODBC data source and drill down to our new dataset. 👁 Selecting the Okta Dataset (Salesforce is shown).
   
3. With the dataset selected, choose to create a visualization.
4. In the new card:
   • Drag a Dimension to the X Value.
   • Drag a Measure to the Y Value.
   • Choose a Visualization.
   👁 Visualizing Okta Data in Domo (Salesforce is shown).
   

With the CData ODBC Driver for Okta, you can build custom datasets based on Okta data using only SQL in Domo Workbench and then build and share visualizations and reports through the Domo service.