Skip to main content
The Okta replica implements 31 endpoints of the Management API v1 for one org: users with their lifecycle states, groups, applications, app assignments and the System Log. Its key is okta. It was tested with @okta/okta-sdk-nodejs.

Connect

Node
This is what ancha connect okta --lang ts prints.

Endpoints

All 31 endpoints are partial. Anything else returns HTTP 501 with Okta’s error shape and x-ancha-gap: 1.

Users

Groups

Applications

System Log

Behavior

  • One org, acme, and one SSWS token owned by the super administrator ancha@acme.example.
  • Lifecycle changes are immediate. Activation and reset links are returned in the response, never emailed.
  • The System Log holds the seeded events and every change the agent makes.

Starter data

The okta-starter dataset is the org Acme.

Checks

Okta has no state checks. Use trace checks, for example { called: "POST /api/v1/users/*/lifecycle/unlock" } or { not_called: "DELETE /api/v1/users/*" }.

Limits

  • One org and one SSWS token; no OAuth service apps, factors, policies or sign-in flows.
  • Nothing is emailed: activation and reset links come back in the response.
  • The System Log gives no polling next link.