Build Okta-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Okta enables users to access live Okta data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Okta data to any data source natively supported in Google Data Fusion, this article walks through piping data from Okta to Google BigQuery,

Upload the CData JDBC Driver for Okta to Google Data Fusion

Upload the CData JDBC Driver for Okta to your Google Data Fusion instance to work with live Okta data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdataokta-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.okta) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.okta.OktaDriver)
5. Click "Finish"

Connect to Okta Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live Okta data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-okta)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for Okta. For example:
     
     jdbc:okta:RTK=5246...;Domain=dev-44876464.okta.com;InitiateOAuth=GETANDREFRESH;

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

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the Okta JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.okta.jar

     Fill in the connection properties and copy the connection string to the clipboard.

   • Set Import Query to a SQL query that will extract the data you want from Okta, i.e.:
     SELECT * FROM Users
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like okta-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert Okta data into

With the Source and Sink configured, you are ready to pipe Okta data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Okta and import it into Google BigQuery.

While this is a simple pipeline, you can create more complex Okta pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Okta and start working with your live Okta data in Google Data Fusion today.