T13.9: sign in to the Okta Management API as an OAuth service app, private_key_jwt (D23)

This commit is contained in:
2026-10-16 15:29:32 -07:00
parent ad1b8273c0
commit d137d690f9
7 changed files with 422 additions and 11 deletions

View File

@@ -370,3 +370,21 @@ and the third is logged:
1. The web server publishes no port (the host's reverse proxy reaches it). The override publishes 8080 on loopback.
2. An existing `proxy` network on a PC can have no gateway, and Docker then does not publish ports. The override uses its own bridge. The stock nginx `default.conf` also answers "localhost" first and the app server answers only wp.controls.dev, so the override removes the stock file and makes the app server the default.
3. The backup container cannot start on Windows: `scripts/entrypoint.sh` has CRLF line endings (BL-070). The override turns the backup service off.
## T13.9: D23 sign in as an OAuth service app (private_key_jwt)
**Item:** D23 (`docs/waves/decisions-2026-10-16.md`). Extends T13.2.
**Done when:**
- [x] with `OKTA_SYNC_CLIENT_ID` and `OKTA_SYNC_PRIVATE_KEY`, the sync gets an access token and lists users with `Bearer` (`tests/okta_sync_oauth_check.py`)
- [x] the assertion verifies against the public key: `iss`, `sub`, `aud`, `kid`, life, `jti`
- [x] RSA and EC keys; JSON and base64 forms
- [x] a failed token request, a missing token, a DPoP token, a public key, or an unreadable key raises, and the users endpoint is never called
- [x] `OKTA_API_TOKEN` still works and wins when both are set
- [x] the startup line names the credential and holds no secret; no error message holds key text
- [x] mutation checks: Bearer to SSWS, wrong `aud`, DPoP accepted, public-key check removed: each makes the test fail
- [x] `.env.example`, `docker-compose.yml`, `DEPLOYMENT.md` describe the variables and the Okta app setup
Result 2026-10-16: sandbox, fake Okta. Not yet run against the real tenant.
No new dependency: PyJWT signs with `cryptography`, which Authlib already installs.