Interface contract map
The API space is split by resource families and lifecycle mode: discover, read, write, disable, reconcile, and error recovery all carry explicit expectations for Okta clients and FreeIPA-backed operations.
Integration expectations
- Every integration must support tokenized auth and idempotent user lifecycle semantics.
- Discovery endpoints such as
/scim/v2/ServiceProviderConfig,/Schemas, and/ResourceTypesshould be accurate before provisioning rollout. - Filters and paging should stay inside the implemented grammar to avoid unplanned response amplification.
- Client behavior should capture both status and correlation headers for replay diagnostics.
Read first
SCIM protocol contract checks
Pagination
Default and max page size must be explicit and bounded.
Filtering
Grammar mismatch must return structured errors with deterministic remediation.
Mutations
Idempotent writes require stable client keys and correlation context.