Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Build an OLAP Cube in SSAS from Okta Data
Establish a connection to Okta data data from SQL Server Analysis Services, and use the Okta Data Provider to build OLAP cubes for use in analytics and reporting.
SQL Server Analysis Services (SSAS) serves as an analytical data engine employed in decision support and business analytics, offering high-level semantic data models for business reports and client applications like Power BI, Excel, Reporting Services reports, and various data visualization tools. When coupled with the CData ADO.NET Provider for Okta, you gain the capability to generate cubes from Okta data, facilitating more profound and efficient data analysis.
In this article, we will guide you through the process of developing and deploying a multi-dimensional model of Okta data by creating an Analysis Services project in Visual Studio. To proceed, ensure that you have an accessible SSAS instance and have installed the ADO.NET Provider.
Creating a Data Source for Okta
Start by creating a new Analysis Service Multidimensional and Data Mining Project in Visual Studio. Next, create a Data Source for Okta data in the project.
- In the Solution Explorer, right-click Data Source and select New Data Source.
- Opt to create a data source based on an existing or new connection and click New.
- In the Connection Manager, select CData ADO.NET Provider for Okta, enter the necessary connection properties, and click Next.
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:
- Sign in to your Okta developer edition organization with your administrator account.
- In the Admin Console, go to Applications > Applications.
- Click Create App Integration.
- For the Sign-in method, select OIDC - OpenID Connect.
- For Application type, choose Web Application.
- Enter a name for your custom application.
- Set the Grant Type to Authorization Code. If you want the token to be automatically refreshed, also check Refresh Token.
- 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.
- In the Assignments section, either select Limit access to selected groups and add a group, or skip group assignment for now.
- Save the OAuth application.
- 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.
- Check the Assignments tab to confirm that all users who must access the application are assigned to the application.
- 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 connection, 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.
- Set the impersonation method to Inherit and click Next.
- Name the data source (CData Okta Source) and click Finish.
Creating a Data Source View
After you create the data source, create the data source view.
- In the Solution Explorer, right-click Data Source Views and select New Data Source View.
- Select the data source you just created (CData Okta Source) and click Next.
- Choose a foreign key match pattern that matches your underlying data source and click Next.
- Select Okta tables to add to the view and click Next.
- Name the view and click Finish
Based on the foreign key match scheme, relationships in the underlying data will be automatically detected. You can view (and edit) these relationships by double clicking Data Source View.
Note that adding a secondary data source to the Data Source View is not supported. When working with multiple data sources, SSAS requires both sources to support remote queries via OpenRowset which is unavailable in the ADO.NET Provider.
Creating a Cube for Okta
The last step before you can process the project and deploy Okta data to SSAS is creating the cubes.
- In the Solution Explorer, right-click Cubes and select New Cube
- Select "Use existing tables" and click Next.
- Select the tables that will be used for measure group tables and click Next.
- Select the measures you want to include in the cube and click Next.
- Select the dimensions to be created, based on the available tables, and click Next.
- Review all of your selections and click Finish.
Process the Project
With the data source, data source view, and cube created, you are ready to deploy the cube to SSAS. To configure the target server and database, right-click the project and select properties. Navigate to deployment and configure the Server and Database properties in the Target section.
After configuring the target server and database, right-click the project and select Process. You may need to build and deploy the project as a part of this step. Once the project is built and deployed, click Run in the Process Database wizard.
Now you have an OLAP cube for Okta data in your SSAS instance, ready to be analyzed, reported, and viewed. Get started with a free, 30-day trial of the CData ADO.NET Provider for Okta.