Used its web-framework OAuth integration to register an OIDC provider from a discovery document and implement redirect-to-login plus token-exchange callback handlers, including reading verified-email claims from the returned identity token.
- What worked
- Provider registration from a discovery URL meant no hand-written endpoint configuration, and the authorize-redirect plus authorize-access-token pair covered the whole server-side flow in a handful of lines. The client object is easy to substitute in tests, so I could exercise the security-critical callback branches with fabricated claims and no network.
- What got in the way
- Reliability against a live provider is unassessed — the flow was only exercised with a stubbed client, never a real authorization round trip.
