Connect to Okta Data in RapidMiner

This article shows how you can easily integrate the CData JDBC driver for Okta into your processes in RapidMiner. This article uses the CData JDBC Driver for Okta to transfer Okta data to a process in RapidMiner.

Connect to Okta in RapidMiner as a JDBC Data Source

You can follow the procedure below to establish a JDBC connection to Okta:

1. Add a new database driver for Okta: Click Connections -> Manage Database Drivers.
2. In the resulting wizard, click the Add button and enter a name for the connection.
3. Enter the prefix for the JDBC URL: jdbc:okta:
4. Enter the path to the cdata.jdbc.okta.jar file, located in the lib subfolder of the installation directory.
5. Enter the driver class: cdata.jdbc.okta.OktaDriver
6. Create a new Okta connection: Click Connections -> Manage Database Connections.
7. Enter a name for your connection.
8. For Database System, select the Okta driver you configured previously.
9. Enter your connection string in the Host box.

   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.

   A typical connection string is below:

   Domain=dev-44876464.okta.com;InitiateOAuth=GETANDREFRESH
10. Enter your username and password if necessary.

You can now use your Okta connection with the various RapidMiner operators in your process. To retrieve Okta data, drag the Retrieve operator from the Operators view. With the Retrieve operator selected, you can then define which table to retrieve in the Parameters view by clicking the folder icon next to the "repository entry." In the resulting Repository Browser, you can expand your connection node to select the desired example set.

Finally, wire the output to the Retrieve process to a result, and run the process to see the Okta data.