feat(backend,clerk-js,types): Support the new LinkedIn OAuth Provider #1772
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: c7d8425 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
fragoulis
force-pushed
the
fragoulis/usr-340-js-support-the-new-linkedin-v2-oauth-provider
branch
from
0ec5bf3 to
a929d10
Compare
anagstef
approved these changes
Sep 25, 2023
fragoulis
force-pushed
the
fragoulis/usr-340-js-support-the-new-linkedin-v2-oauth-provider
branch
from
097f346 to
0b4094a
Compare
SokratisVidros
approved these changes
Sep 28, 2023
nikosdouvlis
requested changes
Sep 29, 2023
LinkedIn has changed the OAuth flow by replacing it with OpenID Connect. We have already added support for this in the backend.
fragoulis
force-pushed
the
fragoulis/usr-340-js-support-the-new-linkedin-v2-oauth-provider
branch
from
14519a0 to
c7d8425
Compare
|
This is ready. The new provider's name will be set in dashboard, as well as whether a user can enable only one of these. |
nikosdouvlis
approved these changes
Oct 10, 2023
desiprisg
reviewed
Oct 10, 2023
| provider: 'linkedin_oidc', | ||
| strategy: 'oauth_linkedin_oidc', | ||
| name: 'LinkedIn', | ||
| docsUrl: 'https://clerk.com/docs/authentication/social-connections/linkedin-oidc', |
There was a problem hiding this comment.
This does not exist yet, right? Are we adding it?
There was a problem hiding this comment.
fragoulis
deleted the
fragoulis/usr-340-js-support-the-new-linkedin-v2-oauth-provider
branch
Merged
|
This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
LinkedIn has changed the OAuth flow by replacing it with OpenID Connect. We have already added support for this in the backend.
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change
Packages affected
@clerk/clerk-js@clerk/clerk-react@clerk/nextjs@clerk/remix@clerk/types@clerk/themes@clerk/localizations@clerk/clerk-expo@clerk/backend@clerk/clerk-sdk-node@clerk/shared@clerk/fastify@clerk/chrome-extensiongatsby-plugin-clerkbuild/tooling/chore