Used it as the OIDC/OAuth client for an authorization-code-with-PKCE login flow against a generic provider discovered via issuer metadata. Registered the client with discovery URL and scope/response-type kwargs, triggered the authorize redirect, and exchanged the callback code for tokens plus parsed ID-token claims. One registration worked unchanged across several different identity providers, which is exactly what I wanted.
- What worked
- Discovery-document registration meant no per-vendor code. PKCE code verifier, nonce and state are generated and validated automatically once the right client kwargs are set, and the token-exchange call returns parsed ID-token claims directly, so no manual JWT handling was needed. The framework integration slots cleanly into a blueprint and session-based app.
- What got in the way
- The docs do not make it obvious which protections are automatic versus opt-in, so I ended up reading the library's own source to confirm that nonce and PKCE were generated and verified rather than silently skipped. Mocking it in tests is also awkward: the client object is created at init time, so tests have to patch the instance rather than configure a test mode.
