That shutdown would not affect the plugin. They are shutting down Google Plus and relevant APIs. Google Sign in is still there. Don’t worry. Will include Yahoo login in upcoming releases.
Can you update the G+ buttons to simple “G” buttons to avoid confusion?
Thread Starter
s k
(@subhanjankayet)
actually I updated from your old plugin. I used http://support.heateor.com/tag/google-login/ this url to setup and here you mentioned to enable Google+ api for the social login. ALso I got mail from google that currently I am using it in the project which will be turned off. I am confused then why you told to enable google+ api while installing?
Will update the login button ASAP.
P.S.:The exact date of Google+ and Google+ API shutdown is March 7, 2019. There is no problem with using the Google+ API or/and Google Plus before this.
Hi,
Thanks, it is a relief to read that the Google Social login will still be working after Google+ shutdown.
However, I am still a bit nervous since all your documentation (here and here) refers to the Google+ API and I have received an email from Google stating I am using the Google+ OAuth API for social login and this one will be discontinued.
When browsing the developer console, it also clearly states it is a Google+ API…
Here’s a capture of the email I received: https://i.imgur.com/pmUwYKN.png
How do we go about migrating from Google+ Sign-in to Google Sign-in auth system?
@wcube I have updated the Google Client steps. You don’t need to enable Google+ API. Even if you do, it won’t be used until you are using Google+ scopes in the authentication requests. There isn’t any Google+ scope being used in the plugin.
Now I just need to replace the Google+ signin button with the Google Signin button.
Topic to be followed consistently.
I remember that I had to select the “Google+ API” in their API list to enable social login.
It seem that the Google login has to be done an other way.
A few links in this Drupal forum post @ drupal :
– Google Sign-in
– Integration for Web
+ Google+ @ Github where it states that “If your apikey is a v2 Aouth key, your problem is fixed.” Does it however concern our case here?
PS: 7 march is the dead-line, but the service will stop working slowly until then and starting end January. So
-
This reply was modified 7 years, 3 months ago by
tdechangy.
-
This reply was modified 7 years, 3 months ago by tdechangy.
@tdechangy
See the OAuth 2.0 link at the bottom-left of the page https://developers.google.com/identity/
The process is the same with only difference being you don’t need to enable Google+ API. Even if you have enabled the API at the moment, it won’t affect the Google login as not any of the Google+ scopes is being used by the plugin.
+ Google+ @ Github where it states that “If your apikey is a v2 Aouth key, your problem is fixed.” Does it however concern our case here?
See following answer at the Github page:
If your apikey is a v1 Aouth key, you will fall on the deprecated problem next march
the v1 format is looking like that: AIzaSyxxxxxxLyqMRcivb_gg6tcxxxxxxLmAg
If your apikey is a v2 Aouth key, your problem is fixed.
The v2 format is like: 8368xxxxxx23-uke25fmjdxxxxxxxx9a8r2iur302joa2.apps.googleusercontent.com
You are already using V2 OAuth key.
Thanks for confirming how to validate which version of the API key we are using. I feel relieved.
