403 error in google auth about socialite HOT 13 CLOSED

Can you post the links to the places where you asked for help? This would help us find out what the problem is faster.

from socialite.

from socialite.

This isn't a link to stackoverflow like you said. Looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

• Laracasts Forums
• Laravel.io Forums
• Discord
• Larachat
• IRC
• StackOverflow

from socialite.

from socialite.

Hi,

This is an issue that is happening for me too. I have tried all solutions from several links on stackoverflow and laracasts found via a google search.

For me, I have a test website and live website... https://test.mysite.com and https://www.mysite.com. The odd thing is that this was fully tested and working (and still does) on the test domain, but give me a 403 error when using google on the live domain. Other providers (Facebook/Twitter/Linkedin) all work properly still on both test and live.

From the suggestions relating to 'scope', if I manually edit the callback URL to edit the scopes and press enter, the login process completes. (see below)

https://www.mysite.com/login/google/callback?code=HIDDEN-CODE&scope=openid%20email%20profile%20https://www.googleapis.com/auth/plus.me%20https://www.googleapis.com/auth/userinfo.profile%20https://www.googleapis.com/auth/userinfo.email&authuser=2&hd=HIDDENUSER&session_state=SESSION&prompt=consent

remove the scopes that are NOT within GoogleProvider.php $scopes

https://www.mysite.com/login/googlecallback?code=HIDDEN-CODE&scope=openid%20email%20profile&authuser=2&hd=HIDDENUSER&session_state=SESSION&prompt=consent

EDIT:

N.B removing scopes within the URL on test.mysite.com is not needed - it just works.

from socialite.

@benjam-es can you try upgrading to the latest laravel and socialite version?

from socialite.

The project is currently heavily tied to Laravel 5.5.x meaning im stuck on Socialite v3.x at the moment.

from socialite.

@benjam-es does using the solution from here work? #319 (comment)

from socialite.

From bugsnag also if this helps

public function user()
   {
   if ($this->hasInvalidState()) {
   throw new InvalidStateException;
 }
  
$response = $this->getAccessTokenResponse($this->getCode());

Laravel\Socialite\Two\InvalidStateException
vendor/laravel/socialite/src/Two/AbstractProvider.php:209 Laravel\Socialite\Two\AbstractProvider::user

from socialite.

@benjam-es does using the solution from here work? #319 (comment)

I've now pulled in that dev branch, and am still getting the same problem.

from socialite.

from socialite.

Not sure what that URL is for.. perhaps to do with my previous typo of NOT instead of NOW?

It's just a homepage of tutorials unrelated to this issue.

from socialite.

@benjam-es unfortunately we don't support 3.0 anymore. You'll have to upgrade and see if the newer version helps.

from socialite.