Skip to main content
Use the @bijection/connectors/okta entrypoint to declare Okta resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Users

users: Users with System Log or event-hook hints and lifecycle transitions

The following example matches configuration systemLog.

Configuration: systemLog

Case: okta/users/users/systemLog. Connection and resource configuration are declared by this exact case. Credential kind: okta. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: users
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: eventHooks

Case: okta/users/users/eventHooks. Connection and resource configuration are declared by this exact case. Credential kind: okta. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: users
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: transitions

Case: okta/users/users/transitions. Connection and resource configuration are declared by this exact case. Credential kind: okta. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: users
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection’s setup names the org origin (orgUrl, such as https://example.okta.com) and holds an okta credential (okta.credential): a keyword envelope writing Authorization: SSWS <token>. An API token carries its minting admin’s privileges. Identity is the org id from GET /api/v1/org. Users are listed from GET /api/v1/users, paged by the Link header. The listing omits DEPROVISIONED users and a deleted user answers 404 with no tombstone, so the listing claims no coverage and only the daily point-read sweep’s 404 withdraws a user. updates selects the change hints:
  • systemLog polls GET /api/v1/logs oldest first, filtered to user.* events, including the typed user.lifecycle.delete.* events that announce a deletion. The opaque after cursor is read from the response’s rel="next" link, and Okta retains the log for ninety days.
  • eventHooks admits Okta event hooks. Okta signs nothing: the hook carries the header value the operator chose when registering it, installed as the listener’s signing credential (configured_token on authorization), so a delivery proves only a refresh hint. The one-time x-okta-verification-challenge GET is answered on the same endpoint.
With a governingRule, the lifecycle transitions unlock, suspend, unsuspend and deactivate are commands under a target_state condition: one attempt, no idempotency, and the refusals E0000032, E0000038 and E0000016 read as a lost conditional write. Only E0000032 is in the probe’s evidence; the other two are documented. A lost answer stays unknown: the reconcile read shows the user’s status now, never whose transition produced it. Nothing here has run against Okta or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.