Integration: Okta

Argent with Okta

Argent Strategic Intelligence reads your people and groups from Okta, so every AI agent answers to a real, active person. When Okta says someone has left, their agents stop.

01 / INTEGRATION: OKTA

What Argent does with Okta

Okta already knows who works for you. Argent uses that list to decide which AI agents may act.

  • People, groups and memberships. Argent pulls them from Okta, together with each person's state (active, suspended, deprovisioned).
  • An owner for every agent. Every agent registered with Argent must have an active human owner, and Argent checks that owner on every request. People from Okta are those owners. See Identity Tethering.
  • No owner, no answer. A request from an agent whose owner is missing or switched off is refused, and nothing reaches the AI model.
  • Attribute mapping, reviewed by a person. Argent reads the fields Okta exposes and proposes how they map onto Argent's (who is who, email, status, department). An admin reviews it, edits it and saves it as a new version; earlier versions stay on record.
  • Groups become access. Okta groups map onto Argent grants under Access, versioned, so access follows the directory instead of hand-made lists.
  • Okta Cross App Access. Argent's MCP authorization server accepts an Okta Identity Assertion JWT Authorization Grant (ID-JAG), redeemed as a standard RFC 7523 JWT-bearer grant. An agent working for a signed-in Okta user gets governed tool access without a second prompt, and only the Okta issuers pinned for your tenant are trusted. See controlling agent tool access.
  • Okta over SCIM too. If you would rather have Okta push people into Argent, point it at Argent's SCIM 2.0 endpoint with the okta dialect.
02 / INTEGRATION: OKTA

How it connects

A read-only pull. Argent reads from Okta on a schedule; nothing in Okta is changed.

  1. In the Argent console, open Integrations, Identity sources and choose Add connector, type Okta.
  2. Give it a display name and enter the settings below.
  3. Connect, then Test: Argent pulls a sample from Okta to prove the link works end to end.
  4. Open Attribute mapping, run the mapper, review the proposal and save it. Saving the first mapping version turns the connector on.
  5. Check the result under Identities, People: each person shows OKTA as their source.
03 / INTEGRATION: OKTA

What you configure

SettingWhat to enter
Org URLYour Okta org address, for example https://yourcompany.okta.com.
API tokenAn Okta API token, stored in your vault. Argent is given only its vault path.
Auth schemeLeave at SSWS for a standard Okta API token; choose Bearer only for an OAuth bearer token.
Page sizeOptional. Default 200 records per page.

Argent keys each person on the Okta user id, not the email, so a renamed address does not create a second person.

  • The secret stays in your vault. Argent's configuration holds only the vault path of the credential, never the credential itself. Argent works with HashiCorp Vault and OpenBao, AWS Secrets Manager, CyberArk Conjur and Infisical.
  • Guarded dial-out. Every identity connector dials out through a guarded client that refuses private, loopback, link-local and cloud-metadata addresses. Turn on the egress allowlist and only the addresses you list are reachable (Okta is outside your network, so list its addresses when the allowlist is on).
04 / INTEGRATION: OKTA

When someone leaves, their agents stop

Argent does not have to wait for Okta to send an event. On its next check it compares who is still active with the people it holds.

  1. Switched off in Argent. A person who is missing from Okta, or switched off there, is deactivated in Argent. The change is signed into the audit record in the same step.
  2. Their agents are held. The keys of every agent that person owns are held, and each request from those agents is refused before it reaches a model.
  3. Access removed. Their access in Argent is removed in the same transaction, so nothing they were granted lingers.
  4. Your hand decision sticks. A person an admin switched off by hand stays off, even if a later directory sync reports them active. Only an admin can turn them back on.

A leaver is not deleted. Their agents are refused, held and kept on the record until an admin hands them to a new owner. See Owner Offboarding.

05 / INTEGRATION: OKTA

Where it fits in Argent

Identity sources Argent connects to

Okta and the other identity vendors Argent connects to. Open any logo for its page. SailPoint's mark opens IdentityIQ. Also see SailPoint Identity Security Cloud.

  • Okta
  • Microsoft Entra ID
  • Auth0
  • Keycloak
  • SailPoint
  • Saviynt
  • Ping Identity