Skip to main content

Okta

Okta is an identity and access management platform that controls how your workforce signs in to the SaaS applications your organization uses. Nexla connects to the Okta Management API to ingest users, app integrations, app assignments, groups, admin role holders, and System Log sign-in events. Together these answer the core SaaS app inventory and license usage questions: which apps exist, who is assigned to each one, and when each person last signed in.

Okta icon

Power end-to-end data operations for your Okta API with Nexla. Our bi-directional Okta connector is purpose-built for Okta, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Okta or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Okta workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla authenticates to Okta with an Okta API token. Every request is sent to your Okta org domain with the header Authorization: SSWS <token>. To create the credential, you need two values:

  • Your Okta domain, such as acme.okta.com or a custom domain such as login.acme.com, entered without https://.

  • An Okta API token, created in the Okta Admin Console.

Okta API tokens are issued for a specific user, and all requests made with the token act on behalf of that user. According to Okta, "API tokens inherit the privilege level of the admin account that is used to create them," and if that user's permissions change, so do the token's. Super admins, org admins, group admins, group membership admins, and read-only admins can create tokens. Because Nexla only reads data from Okta, we recommend creating the token while signed in as a dedicated service account that holds the read-only admin role, rather than using a personal admin account.

To create an API token, follow these steps from the Okta help documentation:

  1. Sign in to the Okta Admin Console as the service account that will own the token.

  2. Go to Security > API, and click the Tokens tab.

  3. Click Create token.

  4. Enter a name for the token in the What do you want your token to be named? field, such as "Nexla".

  5. From the API calls made with this token must originate from dropdown list, select where connections are allowed to come from. Any IP allows connections from any address; the other options restrict the token to network zones defined in your Okta org. Okta only supports IP-based zones for API tokens.

  6. Click Create token, then click Copy to clipboard and store the token in a secure location such as a password manager. This is the only time the token value is shown; Okta stores only a hash of it afterwards.

warning

Okta API tokens are valid for 30 days and renew automatically each time they are used. A token that is not used for more than 30 days is revoked and cannot be used again. Tokens issued by a user who is later deactivated are also rejected. Schedule your Okta flows to run at least once every 30 days, and keep the service account active, so the credential does not stop working. See Create an API token for details.

Okta also supports OAuth 2.0 service apps for the Management API, but those require the private_key_jwt client authentication method, which this connector does not support. Use an API token instead.

Authenticate​

Credentials required​

Okta API token created by an admin (Security > API > Tokens). The token inherits the creating admin's permissions; use a read-only admin service account.

FieldRequiredSecretDescription
Okta DomainYesNoYour Okta org domain without https://, e.g. acme.okta.com or a custom domain such as login.acme.com.
API TokenYesYesThe Okta API token value (sent as Authorization: SSWS <token>).

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your Okta org domain in the Okta Domain field, without the https:// prefix or any path. For example, enter acme.okta.com, or your custom domain such as login.acme.com. Nexla sends all API requests to https://<your domain>/api/v1.

  4. Paste the token you created in the Okta Admin Console into the API Token field. Enter only the token value; Nexla adds the SSWS prefix to the Authorization header automatically.

    The API token is a secret and should be treated like a password. It carries the permissions of the admin account that created it, so create it with a dedicated read-only admin service account. If the token is exposed, revoke it in the Okta Admin Console under Security > API > Tokens and create a new one.

  5. Click the Save button at the bottom of the overlay. Nexla validates the credential by calling the Okta endpoint that returns the current user (/api/v1/users/me). The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Okta connector tile, then select the credential that will be used to connect to your Okta org, and click Next; or, create a new Okta credential for use in this flow.

The Okta connector is a data source only. It reads from Okta and does not write to it.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Okta endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

For a SaaS app inventory and license usage view, the endpoints fit together as follows: List Applications gives the inventory of apps; List Application Users and List Application Group Assignments show who holds each app, directly or through a group; List Users provides each person's status and lastLogin; and List System Log Events shows sign-ins to each app over a time window. The per-app, per-group, and per-user endpoints take an ID returned by the list endpoints.

List Users

Returns all users in the org with their status, created, activated, and lastLogin timestamps, and profile.

  • Search Expression (optional, default empty): An Okta search expression that narrows the results, such as status eq "ACTIVE" or lastUpdated gt "2026-01-01T00:00:00.000Z".
  • Without a search expression, Okta omits deprovisioned users. To list them, enter status eq "DEPROVISIONED".

Sends GET /api/v1/users?limit=200 and reads each user from the top-level response array. Additional pages are fetched by following the Link response header. See the Okta List Users reference.

List Applications

Returns all app integrations in the org, with their status and sign-on mode. This is the SaaS app inventory.

  • Filter (optional, default empty): A filter expression that narrows the results, such as status eq "ACTIVE".

Sends GET /api/v1/apps?limit=200 and reads each app from the top-level response array. Additional pages are fetched by following the Link response header. The id field of each app is the Application ID used by the per-app endpoints below. See the Okta List Applications reference.

List Application Users

Returns the users assigned to one app, with their assignment status, scope, and app profile.

  • Application ID (required, no default): The ID of the app, taken from the id field returned by List Applications.

Sends GET /api/v1/apps/<Application ID>/users?limit=500 and reads each assignment from the top-level response array. Additional pages are fetched by following the Link response header. See the Okta List Application Users reference.

List Application Group Assignments

Returns the groups assigned to one app. A group assignment grants the app to every member of the group.

  • Application ID (required, no default): The ID of the app, taken from the id field returned by List Applications.

Sends GET /api/v1/apps/<Application ID>/groups?limit=200 and reads each group assignment from the top-level response array. Additional pages are fetched by following the Link response header. Combine with List Group Members to resolve which users receive the app through a group. See the Okta List Application Group Assignments reference.

List Groups

Returns all groups in the org.

  • This endpoint has no configurable parameters.

Sends GET /api/v1/groups?limit=1000 and reads each group from the top-level response array. Additional pages are fetched by following the Link response header. The id field of each group is the Group ID used by List Group Members. See the Okta List Groups reference.

List Group Members

Returns the users who are members of one group.

  • Group ID (required, no default): The ID of the group, taken from the id field returned by List Groups.

Sends GET /api/v1/groups/<Group ID>/users?limit=1000 and reads each user from the top-level response array. Additional pages are fetched by following the Link response header. See the Okta List Group Members reference.

List User App Links

Returns the apps assigned to one user, as shown on that user's Okta dashboard.

  • User ID (required, no default): The ID or login of the user, such as the id field returned by List Users.

Sends GET /api/v1/users/<User ID>/appLinks as a single request and reads each app link from the top-level response array. See the Okta List App Links reference.

List System Log Events

Returns audit events in a time window, including sign-ins to each app (event type user.authentication.sso), app assignments, and user deactivations.

  • Since (required, default {now-7}): The start of the time window, in ISO 8601 format. The default is 7 days before the run.
  • Until (required, default {now}): The end of the time window, in ISO 8601 format. The default is the time of the run.
  • Filter (optional, default empty): A SCIM filter expression, such as eventType eq "user.authentication.sso" to return only app sign-in events.

Sends GET /api/v1/logs with the since, until, and filter values, limit=1000, and sortOrder=ASCENDING, and reads each event from the top-level response array. Additional pages are fetched by following the Link response header. Okta does not return System Log data older than 90 days. See the Okta System Log query guide and the List all System Log events reference.

Keep Until set. When a System Log request has no until value, Okta treats it as a polling query: the response always includes a next link, even when there are no new events, so pagination never ends. With both since and until set, the query is bounded and the last page has no next link.

List Users with Admin Roles

Returns the users who hold an admin role assignment.

  • This endpoint has no configurable parameters.

Sends GET /api/v1/iam/assignees/users?limit=100 and reads each user from the top-level response array. Additional pages are fetched by following the Link response header. See the Okta List all users with role assignments reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Okta data sources can also be manually configured to ingest data from any valid Okta Management API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Okta Management API endpoints follow the pattern https://<your Okta domain>/api/v1/<resource>, and most list endpoints return a top-level JSON array (path to data $[*]). Okta paginates them with the Link response header: each page includes a rel="next" link carrying an after cursor until the last page. List Users with Admin Roles is the exception: it returns an object with the users under value (path to data $.value[*]) and the next page in _links.next.href. Okta recommends following these links rather than building cursor URLs yourself. The Authorization: SSWS header is added automatically by your credential. For more information, see Pagination in the Okta API reference.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Okta data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.