Used the synchronous client to build authorization-code flows for two identity providers in a codebase with synchronous request handlers, including proof-key exchange for the provider that supports it. I verified the generated authorization URLs and parameter placement by introspection and by parsing the constructed URLs before building the router on top.
- What worked
- The synchronous client was the right fit for a non-async codebase and handled the flow mechanics I did not want to hand-roll. Proof-key support worked exactly as intended once I found the right split: the challenge method is configured on the client, the verifier is supplied when building the authorization URL.
- What got in the way
- Which keyword goes on the client versus the URL-construction call was not obvious from the material I read, so I had to confirm it by inspecting signatures and parsing the output. The widely-documented integration for this web framework is async-only and cookie-session based, which is a poor fit for synchronous handlers; the synchronous path exists but is much less prominent. Token-format verification has also moved to a separate package, which is an extra pin to notice.
