-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update LinkedIn Provider to Use OpenId Connect
#154
Comments
SignInWithLinkedInUsingOpenIdConnect
OpenId Connect
I'm also looking forward to |
Hello, I made a package to connect using LinkedIn openid connect, if you want to create own |
Thanks for the package. I wasted almost a week on this problem, thinking that the error was mine. |
If you have an error on my package you can open an issue here with details and i will help you : https://github.com/LoicOuth/adonis-ally-linkedin-openid-connect/issues 😉 |
@LoicOuth Sorry it took unexpectedly long to look into this issue. Would you be up for creating a PR/merging your package into the official package? I believe, we should create a new driver for LinkedIn with OpenId Connect so that existing apps can continue to work with the old driver even after updating the package, but we can deprecate it within the docs |
I will try to do it this week. Thanks for your response! |
Facing the same issue. |
Package version
5.0.2
Describe the bug
The current LinkedIn provider utilizes the
Sign In With LinkedIn
method, which has been deprecated as of August 2023. LinkedIn has introduced a new method, withOpenId Connect
, which needs to be adopted to ensure the package remains functional and up-to-date.OpenId Connect
involves several changes, including updates to the scopes and some of the APIs used.I would like to propose a PR to update the LinkedIn provider to use the new method. This update will include changes to the scopes and adjustments to the related API calls to ensure compatibility with LinkedIn's latest requirements.
Please let me know if you would like me to proceed with the PR or if there are any other considerations to take into account.
Thank you!
Reproduction repo
No response
The text was updated successfully, but these errors were encountered: