Okta

Okta connects your directory, user accounts (including MFA enrollment) and managed devices, into Navigator.

At a glance

Data providedUsers, Devices
AuthenticationAPI token
Where to configureConnectors → Add a Connector → Okta

Required permissions

CredentialRequired access
API TokenGenerated by an Okta admin account. A Read-Only Administrator role is sufficient. Navigator never writes to Okta; it only reads users, devices, and factor (MFA) enrollment data.

Setup

  1. In the Okta Admin Console, go to Security → API → Tokens and create a new token, using a dedicated read-only admin account rather than a personal admin account where possible.
  2. Note your Okta domain (e.g. your-org.okta.com) and the token value.
  3. In Navigator, go to Connectors → Add a Connector → Okta.
  4. Enter your Okta Domain and API Token.
  5. Save. Navigator validates the credentials and enqueues a first sync immediately.

Vendor documentation

Okta’s own instructions: Create an API token (Okta Developer).

What data this connector provides

  • Users: including real per-user MFA enrollment status and factor types, via Okta’s Factors API (filtered to active factors only).
  • Devices: including a genuine per-device “managed” signal used directly as agent/MDM coverage.
  • Disk encryption status is derived from Okta’s own diskEncryptionType field using Okta’s documented rule (full or all-internal-volumes encryption counts as encrypted).

Known limitations

  • Okta reports device platform values in all caps (e.g. WINDOWS, MACOS), which won’t exactly match how other connectors report the same platform. This is a known, cosmetic inconsistency, not a matching error.
  • Okta devices don’t share a common identifier with Microsoft-connector devices, so cross-connector matching for the same physical device falls back to hostname/serial/MAC overlap rather than an exact directory ID match.
Next → CrowdStrike