Connect to Okta Data from Crystal Reports

Crystal Reports is a business intelligence application by SAP designed to help you analyze your data with well-formatted, pixel-perfect, and multi-page reports. When paired with CData Connect AI, Crystal Reports gets access to live Okta data. This article demonstrates how to connect to Okta using Connect AI and report on Okta data in Crystal Reports.

CData Connect AI provides a pure SQL Server interface for Okta, allowing you to query data from Okta without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to Okta, leveraging server-side processing to return the requested Okta data quickly.

Configure Okta Connectivity for Crystal Reports

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

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

2. Select "Okta" from the Add Connection panel

3. Enter the necessary authentication properties to connect to Okta.

   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.
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add Okta 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 Okta data from Crystal Reports.

Connect to Okta from Crystal Reports using Connect AI

To establish a connection from Crystal Reports to CData Connect AI, you will need to download the JDBC driver.

1. Open the Client Tools page of CData Connect AI.
2. Search for and select JDBC.
3. Download and run the setup file.
4. When the installation is complete, locate the JDBC Connect JAR file in the JDBC driver's installation directory, for example, C:\Program Files\CData\JDBC Driver for CData Connect\lib.
5. Copy the JDBC Connect JAR file (cdata.jdbc.connect.jar).

After copying the JDBC CData Connect JAR file, you will need to paste it into the Crystal Reports installation location and configure the connection to Connect AI.

1. Find the installation directory for Crystal Reports, for example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib
2. Paste the JDBC Connect JAR file into the Crystal Reports installation directory.
3. Go to the parent java folder. For example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java This folder should contain a CRConfig file.
4. Open CRConfig in a text editor.
5. Add the path to the JDBC CData Connect JAR file in the of the CRConfig file, for example, C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib
6. Log into Crystal Reports and start a blank report.
7. In the Database Expert dialog, click Create New Connection.
8. Select the JDBC data source and the tables you want to add. Click OK.
9. In the Connection dialog, enter the Connection URL (e.g. jdbc:connect:AuthScheme=Basic;user=username;password=PAT;) and Database Classname (e.g. cdata.jdbc.connect.ConnectDriver).
10. Click Finish. The Database Expert dialog displays all available connections.

You can now create reports with the connected data.

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Crystal Reports, try CData Connect AI today!