Okta (Edge)

Configure Okta as a Source in your Pipeline

Perform the following steps to configure your Okta Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Okta.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Okta Source.

   • In the Connect to Okta section, specify the following:

     • Subdomain: The subdomain of your Okta organization. For example, acme.

     • Domain: The domain of your Okta organization. For example, okta.com.

     • API Token: The API token that you obtained from your Okta Admin Console. You can change this value after the Pipeline is created.

6. Click Test & Continue to test the connection to your Okta Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. Selecting a parent object automatically includes its child objects. The Data Model lists the child objects of each parent object.

In the first run of the Pipeline, Hevo ingests all the data available for the selected objects in your Okta organization. For the System Log object, Hevo ingests the events of the last 90 days, which is how long Okta retains them. In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:

Hevo ingests the child objects of a parent object along with it. When Hevo ingests a parent record, it replaces the child records of that parent in the Destination.

Okta limits the number of API requests that an organization can make to each endpoint per minute. The limits depend on your Okta subscription, and the API token shares them with the other integrations of your organization. Read Rate limits. If Okta returns a rate limit error, Hevo waits and retries the request. If the limit is still exceeded, the object fails in that run, and Hevo ingests it again in the next run. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Pipelines with this Source support only the Merge load mode.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---