Skip to content
Integrations/Okta/Connection Guide
Connection Guide

Connect Okta Without Breaking the Audit Trail

Use this guide to connect Okta or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryIdentity
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Okta and make sure the first collection lands cleanly.

  1. 1
    Generate an Okta API token with read access to Users, Groups, Policies, Roles, and Factors.
  2. 2
    Configure okta_domain (e.g. dev-123.okta.com) and api_token.
  3. 3
    Validate connection, then run a full sync; incremental uses lastUpdated watermarking.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_token

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.