Login with google api (Symfony4) about oauth2-client-bundle HOT 4 CLOSED

Hey @emiliosa!

Hmm, I can see a few possible problems:

1. public function checkCredentials needs to return true;. Without that, Guard will think that your authentication has failed

2. Remove the public function createAuthenticatedToken method - this is implemented in a base class. By having this, but empty, it should break things.

3. If you change these things, and it still doesn't work, let me know: it's quite possible that authentication IS successful, but your system is having problems reloading the user from the session. To know if this is a problem, you can change the intercept_redirects config to true temporarily (https://github.com/symfony/recipes/blob/fedaf4a81d15d182efa02733db5703bc35e4024d/symfony/web-profiler-bundle/3.3/config/packages/dev/web_profiler.yaml#L3). Then, after logging in with Google, the system will "stop" before redirecting you on success. On this "stopped" page, you will see the web debug toolbar. You can see if you are authenticated or anonymous. If you ARE authenticated... but then become anonymous after following the redirect, then you will know there is a problem reloading the user from the session (and I can help describe the solution).

Cheers!

from oauth2-client-bundle.

Hi, thanks for the quick reply, i was able to fix doing step 1 and 2, now i can login with any user vía google.

Thanks!

from oauth2-client-bundle.

Hi Ryan, I have this error:

" 3) If you change these things, and it still doesn't work, let me know: it's quite possible that authentication IS successful, but your system is having problems reloading the user from the session. To know if this is a problem, you can change the intercept_redirects config to true temporarily (https://github.com/symfony/recipes/blob/fedaf4a81d15d182efa02733db5703bc35e4024d/symfony/web-profiler-bundle/3.3/config/packages/dev/web_profiler.yaml#L3). Then, after logging in with Google, the system will "stop" before redirecting you on success. On this "stopped" page, you will see the web debug toolbar. You can see if you are authenticated or anonymous. If you ARE authenticated... but then become anonymous after following the redirect, then you will know there is a problem reloading the user from the session (and I can help describe the solution)."

Do you know tha cause? Thanks for your help.

from oauth2-client-bundle.

Hey @diegogazzolo!

Yes, I know this error VERY well :). For some reason, there is a problem deserializing your User object from the session.

First, if you have a serialize() method on your User object. Remove it. It could be the problem. Basically, at the beginning of each request, your User object is loaded from the session. Then, Symfony queries for a fresh User object from the database and compares the one from the session with the "fresh" User object. If they are "different", for security reasons, you are logged out. This can happen if you have a serialize() method on User and aren't serializing enough stuff. It can also easily happen if you're implementing the AdvancedUserInterface. Here is the logic Symfony uses to compare the users: https://github.com/symfony/symfony/blob/7135aa43380c26a38524a045b42414efb45cf48f/src/Symfony/Component/Security/Core/Authentication/Token/AbstractToken.php#L241

Let me know if that helps!

from oauth2-client-bundle.