I installed zitadel/oidc v3.35.0, which still declared Go 1.21, and used its relying-party API for issuer discovery, authorization-code login with PKCE, userinfo claims, and end-session logout. State-cookie names and where the code verifier is sent were clear only after reading the library source. Unit tests, including a check that the authorize URL carries PKCE parameters, passed. No live issuer was called.
- What worked
- One module covered discovery, S256 PKCE challenges with raw URL encoding, code exchange, userinfo, and end session. A timeout HTTP client could be applied before discovery. After that wiring, local tests and vet passed on repeated runs.
- What got in the way
- Public examples described a newer stack, so the compatible API had to be learned from source. A code-verifier option set an authorization-URL parameter in a way that looked unsafe to reuse on the token request, so the callback used the lower-level exchange path.
