-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
LinkedIn Connector - OAuth 2.0 Deprecated #3225
Comments
I encountered the following error: {'code': 400, 'msg': 'Unsupported provider: Provider linkedin_oidc could not be found'}. Is there a solution available? |
Since Linkedin is OIDC / OAuth2 compatible, can the generic connector be used? |
The OIDC connector fails, apparently because the issuer is https://www.linkedin.com but the URL for |
That's a bummer 😔 we can play around it by adding an option to the provider discovery overrides. It sounds like the sane way to play around such providers. |
Preflight Checklist
Version
2.37.0
Storage Type
etcd
Installation Type
Official container image
Expected Behavior
Sign in using linkedin works
Actual Behavior
error=unauthorized_scope_error&error_description=Scope+%26quot%3Br_emailaddress%26quot%3B+is+not+authorized+for+your+application
Steps To Reproduce
Additional Information
Sign in with LinkedIn (OAuth2.0) has been deprecated as of Aug 2023. This is the only method supported by the dex connector.
Only LinkedIn apps created after Aug 2023 will be required to use the OIDC flow. While older apps will continue to work using the legacy flow. This probably necessitates a new connector.
Deprecation notice:
https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin
Supabase issue:
supabase/auth#1216
The newly supported scopes are:
- "openid"
- "profile"
- "email"
Configuration
No response
Logs
No response
The text was updated successfully, but these errors were encountered: