Selected Okta as the token issuer and coded the verifier against its known token shape (custom authorization server issuer, JWKS at a fixed path, RS256, scp as an array, cid for client identity) without a live tenant. No actual tokens or JWKS endpoints were exercised; the integration was validated only against a locally minted equivalent.
- What worked
- Standard OIDC discovery and JWKS mean the service code stays vendor-neutral; one issuer can serve both human SSO and client_credentials tokens, which simplifies plugin config.
- What got in the way
- Several Okta-specific gotchas have to be known up front: custom audiences require the API Access Management add-on and a custom authorization server rather than the org server, and scopes arrive as an scp array rather than a space-delimited scope string. These are easy to get wrong without a tenant to test against.
