should help you out OAuth can be used for authentication (knowing who the user is), and authorization (accessing data on behalf of the user). The open standard for doing authentication with OAuth 2.0 is OpenID Connect, which Google supports. The old document titled "OAuth 2.0 for Login (Early version)" referred to an earlier recommendation for how to authenticate users using OAuth 2.0, before OpenID Connect existed. So the only thing deprecated in that doc was this old authentication pattern, in favor of the final, standardized implementation of OpenID Connect. As long as you use OAuth 2.0, and OpenID Connect – you're fine.
What do I need to change for Google+ APIs and OAuth shutdown?
By : user2396103
Date : March 29 2020, 07:55 AM
hope this fix your issue The issue isn't that you use the plus.profile scope, it is that the library uses the HTTP endpoint for plus.people.get to get the profile information. Even if you're not using a plus scope, best practice three years ago was to use the plus endpoints to get profile information. There is a pull request that changes the endpoint that is used. It isn't clear to me why it hasn't been merged, but it should be shortly.