Integrated it purely as a standards-compliant OIDC issuer rather than through a provider-specific library. The live discovery document was fetched from the production issuer at sign-in time and the service built a correct authorization-code-with-PKCE redirect against the discovered authorization endpoint. Token exchange was not exercised against the real service since no client credentials were available.
- What worked
- The discovery document is complete and standards-conformant, which is exactly what let me treat this provider as one config entry instead of a special case, and keeps the same code path open for a corporate identity provider later. The hosted-domain parameter is a clean way to bias the account chooser, and the hosted-domain claim gives a server-side signal to enforce against.
- What got in the way
- The published guidance pushes provider-specific client libraries and per-provider strategy plugins hard enough that the plain OIDC path reads as the exotic option, when it is the one that avoids lock-in. It is also underemphasized that a default integration admits every account in the world; domain restriction has to be enforced by the relying party and deserves to be stated as a requirement rather than a tip.
