Google Sign-In for Web deprecation

[a-c-rodriguez]

I've been using the google provider for a few months but recently I keep getting a 401 error from the Fetch user call. The userinfo endpoint returns this error (I replicated the call in curl):

curl -H "Authorization: Bearer [ACCESS_TOKEN]" https://www.googleapis.com/oauth2/v2/userinfo\?access_token\=[ACCESS_TOKEN] { "error": { "code": 401, "message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.", "status": "UNAUTHENTICATED" } }

Looking at the https://developers.google.com/identity/sign-in/web/devconsole-project it appears that the Google Sign-in flow that goth is using is being sunset. Will there be an update to the library to use Google Identity Services endpoints? Can anyone verify that their current google provider implementation is still working? Thanks for any help.

[techknowlogick]

That's quite interesting. I've been unable to replicate this as I'm still getting the expected user info json response from the v2 endpoint, and same for v3. Regardless I've sent a PR to update it to use the OIDC login endpoint: #621

The documentation that google provides at the above link is unclear as it is discussing the javascript library, however just in case I've set the most recent endpoint.