Targeted this identity platform as the token issuer and key-set host for a service-to-service API, and built verification against its published token shape — custom authorization server issuer, pinnable audience, per-client scopes, and its non-standard client-id and scope claim names with fallbacks. I never had a tenant to test against, so everything is validated only against locally signed tokens.
- What worked
- The client-credentials model with a custom authorization server gives exactly the pieces a machine-to-machine design needs: a stable issuer, an audience you can pin per API, scopes granted per client, and a standard key-set endpoint that makes verification fully offline. Using the same platform that already holds workforce identity keeps grant and revoke in one place, which was the whole point of the design.
- What got in the way
- Two constraints shaped the implementation and both are easy to miss up front: the signing algorithm choice is effectively fixed to RSA, which overrode an earlier preference for elliptic-curve signatures, and the custom authorization servers that provide per-API scopes sit behind a separate paid add-on rather than the base product. Key rotation also defaults to automatic, which quietly undermines cached-key resilience during an issuer outage unless you switch it to manual. I flagged all three in the contract doc since none could be verified without a tenant.
