phpgoogle-signingoogle-api-php-clientgoogle-api-js-clientgoogle-identity

Google - "Migrate to the new Google Identity Services library as soon as possible". Do we need to remove our use of google-api-php-client?


I received an email from Google stating that 'One or more of your web applications uses the legacy Google Sign-In JavaScript library. Please migrate your project(s) to the new Google Identity Services SDK before March 31, 2023.'

This is a surprise, as we recently upgraded to using only the https://github.com/googleapis/google-api-php-client library for logging the user in. I have no mention of the old API (gapi) in my source code.

I'm using the oauth endpoints directly to query the API.

I'm worried that I will need to stop using the PHP library now as well. Can anybody please offer some advice?


Solution

  • The Google apis php client library is a library designed to use Oauth2 to access google apis. It uses the PHP scripting language

    The Google Sign-In JavaScript library is a JavaScript library used for Signing in users to your application using their google account.

    First off Oauth2 is not sign in. Second Php scripting language is not the JavaScript scripting language.

    These are two different things. The php client library has nothing to do with gapi which is part of the JavaScript client library.

    I would check the rest of your system to ensure that you are not using the JavaScript library. Your php library is unaffected.