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

@@ -68,6 +68,19 @@ OKTA_REDIRECT_URI=CHANGE_ME
# stays off (the startup log says so).
# OKTA_API_TOKEN=CHANGE_ME
#
# Second way to sign in to the Management API (D23): an Okta "API Services" app that
# uses client authentication private_key_jwt. Set these two INSTEAD of OKTA_API_TOKEN.
# If OKTA_API_TOKEN is also set, the token is used.
# OKTA_SYNC_CLIENT_ID the client ID of that app (starts with 0oa)
# OKTA_SYNC_PRIVATE_KEY its PRIVATE key as a JWK, as JSON or as base64 of that JSON.
# In Portainer use base64: it has no quote marks to be mangled.
# The Okta app needs the scope okta.users.read granted (Okta API Scopes tab), an admin
# role such as Read-only Administrator assigned to it, and "Require Demonstrating Proof
# of Possession (DPoP)" switched OFF. The key is a secret: never commit it or paste it
# into chat or a ticket.
# OKTA_SYNC_CLIENT_ID=0oaXXXXXXXXXXXXXXXXX
# OKTA_SYNC_PRIVATE_KEY=
# The Okta org URL that serves the Management API, e.g. https://yourorg.okta.com
# Optional. If unset, it is the scheme and host of OKTA_ISSUER. Must be https.
# OKTA_ORG_URL=https://your-org.okta.com