Okta System Log
Collect Okta System Log events with a read-only administrator's API token
Collect Okta sign-ins, MFA, SSO, user and group changes, and administrative events from /api/v1/logs. The system_log stream uses source type okta and parser okta_ocsf.
Setup
This connector uses an SSWS API token. Review the pull permissions matrix.
1. Create the vendor token
As the read-only administrator, open Okta Admin Console → Security → API → Tokens → Create token. Store the token securely. Okta expires a token unused for 30 days; scheduled collection keeps it in use.
2. Add a pull feed
Publish the okta_ocsf parser for the okta log source under Ingestion → Log Sources. Then open Ingestion → Log Sources → Pull feeds, add an Okta System Log feed, and enter:
| Field | Value |
|---|---|
API token (API_TOKEN) | The SSWS API token. Enter the token value; the connector supplies the authentication scheme. |
Okta org domain (OKTA_DOMAIN) | Your org hostname, such as acme.okta.com, without a scheme or path. Use the org domain rather than a custom sign-in domain. |
Allowed org suffixes are .okta.com, .oktapreview.com, .okta-emea.com, .okta-gov.com, and .okta.mil.
Starting the feed needs log_sources:deploy, and entering the token needs credentials:create and credentials:use. On Self-run you can instead install Okta from the Marketplace and supply the same token and domain under Connections → Connect tenant.
3. Verify collection
Check the feed's last status and error on Pull feeds, then its source under Ingestion → Log Sources. Generate a new sign-in event and search:
metadata.log_source="okta" | head 20A created feed alone does not prove delivery.
Streams and fields
The single system_log stream includes the System Log event types exposed by your org. The declarative spec polls every two minutes, with a ten-minute run budget. It walks one-hour windows, delays the upper boundary by 30 seconds, overlaps by two minutes, and starts point-forward, about five minutes before you create the feed. Its event time is published and deduplication key is uuid.
Troubleshoot
Need help with these checks? Contact support with the deployment, request ID and time with timezone.
Authentication or access fails
Check that the token is valid and its creator still has Read-only Administrator access. A rejected token fails collection. Replace expired or revoked tokens in the credential store; never include them in support messages.
The org domain is rejected
Enter the org hostname without https:// or a path. A custom login hostname is not one of the connector's allowed org suffixes.
Rate limits delay collection
The org quota is shared with other clients. The connector honors X-Rate-Limit-Reset on HTTP 429 and slows down as the remaining quota falls. Check other API consumers before increasing polling frequency.
Directory users don't appear
The System Log stream doesn't sync users. Add a separate Okta users identity feed on Pull feeds to sync users and group memberships into nano's user directory.