Used the OAuth2 client plus the PKCE helpers to build a small provider registry, generate authorization URLs with state and a code challenge, and exchange callback codes for tokens. Covered both an OIDC provider and a plain OAuth2 provider from one abstraction, and exercised the flow in tests with stubbed provider endpoints.
- What worked
- The low-level client is flexible enough to drive two quite different providers from one registry, and the PKCE challenge helper is exposed as a plain function so it can be used without buying into a framework integration.
- What got in the way
- The surface is spread across several integration layers and spec-numbered modules, so finding the right import path and confirming where the code challenge method is configured took source introspection rather than a quick doc lookup. A single task-oriented page for 'authorization code with PKCE, no framework' would have saved a round of verification.
