Added new Oauth2Authenticator using the new Symony 5.2 Authenticator …

[Anthodev]

…interface

First draft for the implementation of the new authenticator interface, not sure that's really usable at the moment.

[weaverryan]

Hi there!

thanks for getting this started! I haven’t tested with it yet, but here’s a quick review to get things started. :).

Cheers!

[weaverryan]

Just minor comments!

[Anthodev]

@weaverryan done :)

[weaverryan]

We're close - check out the test failures - I just commented about one. Another is related to needing to run vendor/bin/php-cs-fixer fix locally to fix some phpcs stuff :)

[Anthodev]

Finally done :D

[weaverryan]

Thank you for your hard work @Anthodev!

[Anthodev]

It was too sloppy for my taste, i'll do better next time :p

Thanks anyway @weaverryan ^^

[fcaraballo]

Thank you for this @Anthodev !

[Anthodev]

Thank you @fcaraballo :)

[fliespl]

It's cool example, but how about moving a little further?

Currently it assumes you just create account based only on access_token. Obviously most oauth2 servers will also return refresh token which is worth saving on user entity/document to be able to refresh access token in seperate logic.

With this implementation only access token is avaiable in Badge context.

Also I had to make change to:
$facebookUser = $this->clientRegistry->getClient('facebook_main')->fetchUserFromToken($credentials);

and replace it with:

$facebookUser = $this->clientRegistry->getClient('facebook_main')->fetchUserFromToken(new AccessToken(['access_token' => $credentials]));

That's because first argument of UserBadge expects string (which is taken from AccessToken toString) and fetchUserFromToken method expects and AccessToken object.

[weaverryan]

Good points @fliespl - WDYT about #302?

[fliespl]

@weaverryan left comment to PR.