Designed service-to-service token validation around Okta custom authorization servers: a custom audience and scopes, the client-credentials flow, and local JWKS verification. I never used a live tenant, and tenant setup was left as a manual step. The design relied on my existing knowledge of Okta's standard OIDC behavior, not on docs fetched during the task.
- What worked
- Because Okta follows OIDC standards (issuer, JWKS URI, RS256, cid claim), the integration was vendor-light and easy to test with locally generated keys.
- What got in the way
- The org's default authorization server can't carry custom scopes or audience, so I had to add an explicit startup check that rejects it. That's an easy trap for anyone configuring this.
