Hi @subratamal!
We have received some feedback about 403 errors with Google from our users recently.
What we have noticed so far, users who experienced this issue usually had some kind of firewall, I.e.: ModSecurity
The problem usually is that the firewall does not allow passing http/https links in the URL, but the scopes that Google used loos like:
https://www.example.com/wp-login.php?loginSocial=google&state=12a12a12a12a12a12a12&code=11111111111111111111111111111111111AAAAAAAAAAAAA&scope=https://www.googleapis.com/auth/userinfo.email+https://www.googleapis.com/auth/userinfo.profile
So after the scope there are 2 https urls:
However in the next release of Nextend Social Login we will use the new equivalent scopes:
I am not sure if that will fix the problem, since according to our experiences the old scopes will still appear in the URL that is received after the user authenticated.
Currently it seems like this is a common issue with the Google API:
https://stackoverflow.com/questions/52318115/google-plus-api-problems-with-email-and-profile-scopes
Anyway please get in touch with us directly on:
https://nextendweb.com/contact-us/