Add Okta Data to Informatica Enterprise Data Catalog

Informatica provides a powerful, elegant means of transporting and transforming your data. By utilizing the CData JDBC driver for Okta, you are gaining access to a driver based on industry-proven standards that integrates seamlessly with Informatica's Enterprise Data Catalog. This tutorial shows how to classify and organize Okta data across any environment.

Load the JDBC Driver

To load the JDBC Driver:

1. Install the JDBC Driver on the host running Informatica. For this article, it is assumed that the driver was installed into cdata.jdbc.okta.OktaDriver.
$ java -jar setup.jar
2. Navigate to the JDBC install directory and create a zip file called genericJDBC.zip containing the driver and its license file.
$ cd ~/cdata-jdbc-driver-for-okta/lib $ zip genericJDBC.zip cdata.jdbc.okta.jar cdata.jdbc.okta.lic
3. Move the genericJDBC.zip file into the Catalog Service directory within Informatica. For this article, it is assumed that Informatica is installed into /opt/informatica. Working in this folder will probably require root permissions, so make sure to su or sudo to root before continuing.
# mv genericJDBC.zip /opt/informatica/services/CatalogService/ScannerBinaries
4. Edit the custom deployment configuration to unpack the zip file.
# cd /opt/informatica/services/CatalogService/ScannerBinaries/CustomDeployer/ # nano scannerDeployer.xml

After unpacking the existing ExecutionContextProperty nodes, add a new ExecutionContextProperty node with this content.

<ExecutionContextProperty isLocationProperty="true" dependencyToUnpack="genericJDBC.zip"> <PropertyName>JDBCScanner_DriverLocation</PropertyName> <PropertyValue>scanner_miti/genericJDBC/Drivers</PropertyValue> </ExecutionContextProperty>
5. Refresh the Catalog Service from the Admin console.

Configure the JDBC Resource

To configure the JDBC resource:

1. Open the Catalog administrator and add a new JDBC resource with the following properties:
• Driver Class: cdata.jdbc.okta.OktaDriver
• URL: jdbc.okta: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.

When you configure the JDBC URL, 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.

Typical additional connection string properties follow:

JDBC;MSTR_JDBC_JAR_FOLDER=PATH\TO\JAR\;DRIVER=cdata.jdbc.okta.OktaDriver;URL={jdbc:okta:Domain=dev-44876464.okta.com;};
2. Username: user
3. Password: password

Note that the Username and Password properties are required, even if the driver you are using does not require them. In those cases, you can enter a placeholder value instead.

4. Configure the metadata options to perform at least one source metadata scan. This scan uses the driver to determine what tables, views, and stored procedures are available through the service.
• Source Metadata: Enable this option.
• Catalog: Set this to the appropriate catalog for multi-catalog data sources. Otherwise, set this to CData.
• Schema: Set this to the appropriate schema for multi-schema data sources. Otherwise, set this to the name of the service (for example, Couchbase).
• Case-sensitivity: Generally this option should be disabled. Enable it only for data sources which are case-sensitive.
• Import stored procedures: Enable this if you want to import stored procedure definitions in addition to tables and views.

Other metadata scanners may be enabled as desired.

5. Complete the driver configuration, optionally configuring custom attributes and a scanner schedule.
6. Perform the metadata scan by navigating to the Monitoring tab and clicking Run. Depending upon the data source, this may takes a few minutes.

When the scan is complete, a summary of all of the metadata objects is displayed along with the status of the Metadata Load job. If any errors occur, you can open the Log Location link for the job to see the errors reported by Informatica or the driver.

Validate the Discovered Metadata

Open the Catalog Service browser to view the metadata extracted from the data source. Depending upon the options you selected when configuring the metadata scanner, you may see any combination of tables, views, and stored procedures for the resource you defined.