LinkedIn deprecated OAuth login in favour of OIDC
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.6k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
The [deprecation notice](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin):
> This version of Sign In with LinkedIn has been deprecated as of August 1, 2023. For all Sign In with LinkedIn implementations going forward, please refer to [Sign In with LinkedIn using OpenID Connect](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2).
This leads to a change of scopes: instead of `r_liteprofile`, `r_emailaddress` only the following is now available:
* `oidc`
* `profile`
* `email`
As a consequence, fetching profile in goth now fails with **403 Forbidden** ([here](https://github.com/markbates/goth/blob/492927988958a49753893bce51f9c972dce82929/providers/linkedin/linkedin.go#L116)).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with providers/linkedin/linkedin.go at the profile-fetching code around line 116, then compare its scopes and profile request with LinkedIn's OIDC deprecation notice. Update the LinkedIn integration for the available OIDC scopes and verify that fetching a profile no longer returns 403 Forbidden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100