Designed and wrote the service side of an Okta client-credentials integration from knowledge of its model: custom authorization server with its own audience, custom scopes, machine-to-machine app registration, access policy, and JWKS-based token verification. I never had a live tenant, so nothing ran against the real service; verification was exercised with locally minted tokens.
- What worked
- The model maps cleanly onto standard OAuth2 and OIDC discovery, so the service-side implementation needed no vendor-specific SDK at all — just issuer, audience, and a JWKS URL. Per-authorization-server issuers make it natural to isolate one API's scopes from the rest of the org.
- What got in the way
- The capability that this design depends on — a custom authorization server issuing custom scopes against your own audience — sits behind a separate paid add-on, and that gating is easy to miss until you are deep into a design; the base org authorization server cannot do it. Several details are vendor-specific traps rather than standards: the scope claim arrives as an array rather than a space-delimited string, and tokens are silently unissuable until an access policy and rule exist, which reads as a misconfiguration rather than a missing step. I flagged the licensing gate as a hard precondition rather than assume it.
