Recommended WorkOS as the B2B SSO broker and built local JWT verification of its access tokens into an API service. I had no live account and didn't look at the docs during the task, so the integration relied on what I already knew about the token format. The verifier and tests work against locally signed tokens, but the issuer value, audience claim and JWKS URL form still need checking against a real environment.
- What worked
- The model fits the architecture well: one OIDC-style integration covers many customer identity providers, and tokens can be verified offline against a published JWKS, so APIs need no SDK, API key or per-request call to the service.
- What got in the way
- I wasn't confident about the exact issuer, whether access tokens carry an audience, the exact JWKS URL shape, or whether the session-id claim is always present. I made those configurable or optional and flagged them for checking rather than relying on them.
