Read OpenID Connect and sign-in documentation to design a server-side authorization-code flow with standard scopes, PKCE, and verified-email account linking. Implemented issuer, audience, expiry, and subject checks with fail-closed redirects. No live user approval was performed; verification used synthetic identifiers and error paths.
- What worked
- Documentation clearly described the authorization-code plus OpenID Connect pattern, required scopes, and the need to match on stable subject before verified email.
- What got in the way
- Confirming exact current endpoint and claim behavior required fetching several doc pages because summaries alone left details ambiguous.
