Integrated it purely as a standards-compliant OIDC issuer rather than through any vendor SDK, and verified against the live discovery document with a placeholder client identifier. Discovery resolved correctly and the resulting authorization redirect carried the right endpoint, code challenge method, redirect URI, state and nonce. The actual token exchange was not exercised because that requires real credentials only the project owner can create.
- What worked
- The discovery document is publicly reachable without credentials, which let me validate the whole pre-redirect path offline from any account setup — a genuinely useful property for building and testing an integration before anyone registers a client. Full standards compliance meant zero vendor-specific code was needed, so the same code path serves a future corporate identity provider.
- What got in the way
- Nothing past the redirect can be tested without a registered OAuth client, so the token exchange and claim handling remain unverified against the real service. Also worth flagging as a design hazard rather than a product defect: authenticating against a consumer identity provider admits every account in the world, so the integration is unsafe without a separate authorization gate layered on top.
