T13.10: DPoP for the Okta Management API calls, auto-detected (D24)

This commit is contained in:
2026-10-16 17:10:19 -07:00
parent 83e77ec622
commit 1a3468effd
7 changed files with 490 additions and 40 deletions

View File

@@ -433,15 +433,19 @@ startup log says `Okta sync DISABLED`.
The Okta admin must set up the app as follows: the app type is API Services; the
scope `okta.users.read` is granted on the Okta API Scopes tab; an admin role
that can read users (for example Read-only Administrator) is assigned to the app;
and "Require Demonstrating Proof of Possession (DPoP)" is off. If both
that can read users (for example Read-only Administrator) is assigned to the app.
DPoP can be on or off. By default (`OKTA_SYNC_DPOP=auto`) the sync asks for a plain
token first, and if Okta answers `invalid_dpop_proof` it uses DPoP. Set
`OKTA_SYNC_DPOP` to `on` or `off` only to force one way. If both
`OKTA_API_TOKEN` and the service-app pair are set, the token is used.
The startup line in the log says which credential is in use. A failed sign-in
shows the HTTP status and the Okta error code, for example
`Okta answered HTTP 400 to the token request, error invalid_scope`. Common codes:
`invalid_client` (wrong client ID or key, or the key is not registered on the app),
`invalid_scope` (the scope is not granted), `access_denied` (no admin role assigned).
`invalid_scope` (the scope is not granted), `access_denied` (no admin role assigned), `invalid_dpop_proof` (DPoP was used and Okta
rejected the proof: send the log lines to the developer), `use_dpop_nonce` (Okta kept
asking for a new nonce).
**First deploy: use the dry run.** Set `OKTA_SYNC_DRY_RUN=true` in `.env` (or the
Portainer stack environment) with the token, then run `docker compose up -d --build api`.