Fix linkedin auth considering new apis

[ChrisWayFor]

No description provided.

[XWB]

LinkedinResourceOwnerTest needs to be fixed.

[Khodl]

Any idea how I can contribute to this MR?

How do we ensure that existing "old" apps still work when changing that? Linkedin does not provide the same scopes depending on which kind of app it is:

• New app:
  
• Old app:
  

[Khodl]

In the meantime, we can use the oAuth2 provider:

I did not manage to make it work all the time: I get a REVOKED_ACCESS_TOKEN most of the time, but sometimes it goes through. Definitely strange.

        linkedin:
            type: oauth2
            class: \HWI\Bundle\OAuthBundle\OAuth\ResourceOwner\OAuth2ResourceOwner
            client_id: '%env(LINKEDIN_CLIENT_ID)%'
            client_secret: '%env(LINKEDIN_CLIENT_SECRET)%'
            access_token_url: "https://www.linkedin.com/oauth/v2/accessToken"
            authorization_url: "https://www.linkedin.com/oauth/v2/authorization"
            infos_url: "https://api.linkedin.com/v2/userinfo"

            scope: openid profile email
            user_response_class: HWI\Bundle\OAuthBundle\OAuth\Response\PathUserResponse
            paths:
                identifier: sub
                nickname: given_name
                realname: name

[d9beuD]

@Khodl maybe this answer could help. I'm running into the same issue.

[d9beuD]

How do we ensure that existing "old" apps still work when changing that? Linkedin does not provide the same scopes depending on which kind of app it is:

We could use the same strategy as laravel/socialite#662 (adding a new provider for new apps). linkedin provider stays as it is and we add linkedin_v2 or any other name with @ChrisWayFor's work.

[Khodl]

@d9beuD I like your approach, as it does not break anything. Good job!

[XWB]

Fixed in #2039