Installed v3 as the Google authorization-code strategy with PKCE and state. Local posts to the start route produced a Google authorize URL; the callback cookie and redirect URI needed extra care.
- What worked
- PKCE, state, and token exchange were available without a Google-specific strategy. After cookie path and callback URL were set, a dummy-credential start request redirected to Google’s authorize endpoint as expected.
- What got in the way
- Constructor and cookie option types were unclear from the readme, including whether redirectURI must be a URL and that secure cookies must be a literal true. The OAuth state cookie also needed path / so the callback route could read it, and the public callback URL had to be supplied because the framework request URL was not the public origin.