Auth provider for Linkedin not working #8831

andersengenolsen · 2023-10-10T19:01:31Z

Environment

System:
OS: Linux 6.2 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
CPU: (12) x64 AMD Ryzen 5 3600X 6-Core Processor
Memory: 2.63 GB / 15.53 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.4.0 - /usr/local/bin/node
npm: 9.7.2 - /usr/local/bin/npm

Reproduction URL

https://github.com/nextauthjs/next-auth-example

Describe the issue

As per the documentation from Linkedin, I've set up a new LinkedIn app, and added "Sign In with LinkedIn using OpenID Connect" as a product.

At first I had some problems when not specifying scope.

providers: [ LinkedIn({ clientId: process.env.LINKEDIN_ID, clientSecret: process.env.LINKEDIN_SECRET, }) ], pages: { signIn: '/register-cv' },

This returns an 'unauthorized_scope_error' for r_emailaddress. Managed to fix that issue by providing scopes as per the documentation from Microsoft:

Authenticating Members
New members logging in to your service for the first time will need to follow the Authenticating with OAuth 2.0 Guide. When requesting the authorization code in Step 2 of the OAuth 2.0 Guide, make sure you use the OpenID scope openid to get the ID Token. We are also introducing new scopes profile and email.

openid Required to indicate the application wants to use OIDC to authenticate the member.
profile Required to retrieve the member's lite profile including their id, name, and profile picture.
email Required to retrieve the member's email address.
After successful authentication, you will receive the member's access token and ID token.

If your application does not have these permissions provisioned, you can request access through the Developer Portal. Select your app from My Apps, navigate to the Products tab, and request the Sign in with LinkedIn using OpenID Connect product.

Link: https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2

Updated scopes to match the documentation from Microsoft:

LinkedIn({ clientId: process.env.LINKEDIN_ID, clientSecret: process.env.LINKEDIN_SECRET, authorization: { params: { scope: 'openid profile email' } }})

Now getting this error:

https://next-auth.js.org/errors#oauth_callback_error unexpected iss value, expected undefined, got: https://www.linkedin.com { error: RPError: unexpected iss value, expected undefined, got: https://www.linkedin.com at Client.validateJWT (/home/deb/PhpstormProjects/cvmaker/node_modules/openid-client/lib/client.js:931:15) at Client.validateIdToken (/home/deb/PhpstormProjects/cvmaker/node_modules/openid-client/lib/client.js:766:60) at Client.callback (/home/deb/PhpstormProjects/cvmaker/node_modules/openid-client/lib/client.js:505:18) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async oAuthCallback (/home/deb/PhpstormProjects/cvmaker/node_modules/next-auth/core/lib/oauth/callback.js:109:16) at async Object.callback (/home/deb/PhpstormProjects/cvmaker/node_modules/next-auth/core/routes/callback.js:52:11) at async AuthHandler (/home/deb/PhpstormProjects/cvmaker/node_modules/next-auth/core/index.js:208:28) at async NextAuthApiHandler (/home/deb/PhpstormProjects/cvmaker/node_modules/next-auth/next/index.js:22:19) at async NextAuth._args$ (/home/deb/PhpstormProjects/cvmaker/node_modules/next-auth/next/index.js:108:14) { name: 'OAuthCallbackError', code: undefined }, providerId: 'linkedin', message: 'unexpected iss value, expected undefined, got: https://www.linkedin.com'

How to reproduce

1: Set up new app on Linkedin, add "Sign In with LinkedIn using OpenID Connect" as a product.
2: Add authentication provider for Linkedin:

import LinkedIn from "next-auth/providers/linkedin"

export const authOptions = {
    secret: 'NOT SO SECRET ANYMORE',
    providers: [
        LinkedIn({
            clientId: process.env.LINKEDIN_ID,
            clientSecret: process.env.LINKEDIN_SECRET,
            authorization: { params: { scope: 'openid profile email' } },
        })
    ], pages: {
        signIn: '/register-cv'
    },
}
export default `NextAuth(authOptions);

The text was updated successfully, but these errors were encountered:

andersengenolsen · 2023-10-11T07:47:08Z

SOLVED

After some debugging I managed to solve this. In case anyone else stumbles across this, since it's not well documented:

If you're using Linkedin API V2, you do need to add some custom parameters to the Linkedin provider. The original issue was that the expected iss was undefined. Simply add issuer to OAuthConfig for the Linkedin provider:

issuer: 'https://www.linkedin.com'

This triggers a new error: 'jwks_uri must be configured on the issuer'. Add jwks_endpoint to OAuthConfig:

jwks_endpoint: 'https://www.linkedin.com/oauth/openid/jwks'

Again, this triggers a new error, where nextauth complains that the profile id is missing. Linkedin API V2 use "sub" not "id". Solved by overriding the profile function in OAuthConfig:

             return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email,
                    image: profile.picture,
                }
            }

Complete working provider for Linkedin using Linkedin API V2:

LinkedIn({
            clientId: process.env.LINKEDIN_ID,
            clientSecret: process.env.LINKEDIN_SECRET,
            authorization: { params: { scope: 'profile email openid' } },
            issuer: 'https://www.linkedin.com',
            jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
            async profile(profile) {
                return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email
                }
            },
        })

goerlitz · 2023-10-20T08:36:13Z

This issue should be opened again, because every new app using SignIn with Linked will run into this issue (as I did).

Reason: Microsoft has deprecated the old API as of August 1, 2023!

I'd suggest to keep the current LinkedIn provider as is (for all apps using the legacy API), but add a new LinkedInV2 provider for all new apps using the SignIn with OpenID Connect.

Deprecated API:

New API

andersengenolsen · 2023-10-20T10:35:16Z

Hi,

Fair point. Closed since I managed to solve it by setting some custom parameters, although I used quite some time on it. Reopening.

Either way: Did you manage to get it to work using the provided solution?

goerlitz · 2023-10-20T10:51:46Z

Yes, your solution works great. It saved me a lot of time digging deeper myself. :)

jormaj · 2023-10-20T15:46:16Z

Is it still working for you guys? Even with the snippet posted, I'm still getting an error:
error: invalid_client, error_description: Client authentication failed

(I've double checked the client_id and client_secret multiple times already..

andersengenolsen · 2023-10-20T16:00:55Z

Is it still working for you guys? Even with the snippet posted, I'm still getting an error: error: invalid_client, error_description: Client authentication failed

(I've double checked the client_id and client_secret multiple times already..

It's working. Can you please provide the complete code of [...nextauth.js]? Remember to remove ids and secrets.

jormaj · 2023-10-20T16:06:59Z

Thanks for you reply :)
I got one step 'further': I was using auth.js version 0.12.0. After updating to 0.17.0, I'm now getting a different error:

[mf:inf] GET /auth/csrf 200 OK (1ms)
Called .text() on an HTTP body which does not appear to be text. The body's Content-Type is "application/x-www-form-urlencoded". The result will probably be corrupted. Consider checking the Content-Type header before interpreting entities as text.
[auth][error][SignInError]: Read more at https://errors.authjs.dev#signinerror
[auth][cause]: OperationProcessingError: "response" is not a conform Authorization Server Metadata response
    at processDiscoveryResponse (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:5277:11)
    at getAuthorizationUrl (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:6903:23)
    at async signin (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:6966:14)
    at async AuthInternal (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:7144:27)
    at async Auth (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:7240:28)
    at async respond (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:17685:22)
    at async Object.fetch (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:18172:13)
    at async jsonError (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:18195:12)
    at async jsonError2 (file:///tmp/tmp-17164-QJe0X481iy9Q/hqlw55rde5g.js:18373:12)
[auth][details]: {
  "provider": "linkedin"
}
[mf:inf] POST /auth/signin/linkedin 200 OK (133ms)
[mf:inf] GET /auth/signin 200 OK (2ms)

My code:

SvelteKitAuth(async (event) => {
    const authOptions = {
      providers: [GitHub({
        clientId: GITHUB_ID, clientSecret: GITHUB_SECRET
      }),
      Google({ clientId: GOOGLE_CLIENT_ID, clientSecret: GOOGLE_CLIENT_SECRET }),
      Facebook({ clientId: FACEBOOK_CLIENT_ID, clientSecret: FACEBOOK_CLIENT_SECRET }),
      LinkedIn({
        clientId: LINKEDIN_CLIENT_ID,
        clientSecret: LINKEDIN_CLIENT_SECRET,
        authorization: { params: { scope: 'profile email openid' } },
        issuer: 'https://www.linkedin.com',
        jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
        async profile(profile) {
          return {
            id: profile.sub,
            name: profile.name,
            firstname: profile.given_name,
            lastname: profile.family_name,
            email: profile.email
          }
        },
      })
      ],
      secret: AUTH_SECRET,
      trustHost: true,
      ...
      }
      ```

goerlitz · 2023-10-20T16:14:15Z

I'm using "next-auth": "^4.23.2" - not sure what that auth.js 0.17.0 dependency is.

bholagabbar · 2023-10-20T21:35:47Z

SOLVED

After some debugging I managed to solve this. In case anyone else stumbles across this, since it's not well documented:

If you're using Linkedin API V2, you do need to add some custom parameters to the Linkedin provider. The original issue was that the expected iss was undefined. Simply add issuer to OAuthConfig for the Linkedin provider:

issuer: 'https://www.linkedin.com'

This triggers a new error: 'jwks_uri must be configured on the issuer'. Add jwks_endpoint to OAuthConfig:

jwks_endpoint: 'https://www.linkedin.com/oauth/openid/jwks'

Again, this triggers a new error, where nextauth complains that the profile id is missing. Linkedin API V2 use "sub" not "id". Solved by overriding the profile function in OAuthConfig:
             return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email,
                    image: profile.picture,
                }
            }
Complete working provider for Linkedin using Linkedin API V2:
LinkedIn({
            clientId: process.env.LINKEDIN_ID,
            clientSecret: process.env.LINKEDIN_SECRET,
            authorization: { params: { scope: 'profile email openid' } },
            issuer: 'https://www.linkedin.com',
            jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
            async profile(profile) {
                return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email
                }
            },
        })

God bless, this is the right solution and docs should be updated

mehul1011 · 2023-10-22T15:38:38Z

@andersengenolsen
If you have looked into the API deeply, what is the "sub" prop being returned by them in the response, and how can it be further used?
Also, there is any way to know the users' actual LinkedIn ID (for example: personx is the user ID below)?
https://linkedin.com/personx/

andersengenolsen · 2023-10-22T16:44:25Z

@andersengenolsen If you have looked into the API deeply, what is the "sub" prop being returned by them in the response, and how can it be further used? Also, there is any way to know the users' actual LinkedIn ID (for example: personx is the user ID below)? https://linkedin.com/personx/

Hi,

The sub parameter is an unique user identifier issued "within" the ID token (JWT) from Linkedin API V2 after authenticating. It's simply the user ID.

Documentation available here: https://learn.microsoft.com/en-us/linkedin/consumer/

Also a bit out of scope, since we're discussing Nextauth.. :)

mehul1011 · 2023-10-22T16:48:53Z

@andersengenolsen If you have looked into the API deeply, what is the "sub" prop being returned by them in the response, and how can it be further used? Also, there is any way to know the users' actual LinkedIn ID (for example: personx is the user ID below)? https://linkedin.com/personx/

Hi,

The sub parameter is simply an unique user identifier issued "within" the ID token (JWT) from Linkedin API V2 after authenticating.

The latter seems to be a bit out of scope. Documentation available here: https://learn.microsoft.com/en-us/linkedin/consumer/

Thanks for you response

Basically they have restricted most of the api to a normal developer i believe?
Like for example getting user profile information, also communication api

GustavoContreiras · 2023-11-06T03:38:09Z

I'm still receiving

[next-auth][error][OAUTH_CALLBACK_ERROR] 
https://next-auth.js.org/errors#oauth_callback_error read ECONNRESET {
  error: Error: read ECONNRESET
      at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)
      at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
    name: 'OAuthCallbackError',
    code: 'ECONNRESET'
  },
  providerId: 'linkedin',
  message: 'read ECONNRESET'
}

"next": "^13.5.6",
"next-auth": "^4.24.4",

node 18.18.2
npm 9.8.1

Edit: This is working for me but I'm still receiving OAuthCallbackError intermittently.

LinkedinProvider({
	clientId: process.env.LINKEDIN_CLIENT_ID || '',
	clientSecret: process.env.LINKEDIN_CLIENT_SECRET || '',
	issuer: "https://www.linkedin.com",
	userinfo: {
		url: 'https://api.linkedin.com/v2/userinfo',
	},
	authorization: {
		url: 'https://www.linkedin.com/oauth/v2/authorization',
		params: {
			scope: 'profile email openid',
			prompt: "consent",
			access_type: "offline",
			response_type: 'code'
		},
	},
	token: {
		url: 'https://www.linkedin.com/oauth/v2/accessToken',
	},
	jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
	profile(profile, tokens) {
		const defaultImage = 'https://cdn-icons-png.flaticon.com/512/174/174857.png';
		return {
			id: profile.sub,
			name: profile.name,
			email: profile.email,
			image: profile.picture ?? defaultImage,
		};
	},
})

If you want to use it with an adapter you will need to increase the access_token default column length because Linkedin's access_token has more than 255 characters.

AnatoleT · 2023-11-08T21:45:31Z

Is it still working for you guys? Even with the snippet posted, I'm still getting an error: error: invalid_client, error_description: Client authentication failed

(I've double checked the client_id and client_secret multiple times already..

Hi @jormaj , did you find a workaround for this ? I'm facing the same error..

benjamindell · 2023-11-09T15:55:52Z

Has anyone resolved this? I'm also getting the invalid_client error and can't work out why.

AmitSahoo45 · 2023-11-30T14:36:41Z

I tried the same code in my route.ts inside app/api/auth/[...nextauth] folder:

LinkedInProvider({
            clientId: process.env.LINKEDIN_CLIENT_ID as string,
            clientSecret: process.env.LINKEDIN_CLIENT_SECRET as string,
            authorization: { params: { scope: 'openid profile email' } },
            issuer: 'https://www.linkedin.com',
            jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
            async profile(profile) {
                return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email
                }
            },
        })
    ],

yet still I am running into this error

goerlitz · 2023-12-01T19:49:59Z

Please read the error message completely.
It says "The redirect_uri does not match the registered"
It means that the callbackUrl you passed as parameter in you signIn() function call is not known to LinkedIn. You need to add it to you configuration in LinkedIn.

AmitSahoo45 · 2023-12-02T02:22:56Z

Thanks. Resolved it. 👍🏻

balazsorban44 · 2023-12-12T04:01:01Z

Hi everyone, I'm looking into this now. I think I found a bug in the LinkedIn OIDC implementation, I reached out to them and awaiting response.

benjamindell · 2023-12-12T10:13:54Z

Hi everyone, I'm looking into this now. I think I found a bug in the LinkedIn OIDC implementation, I reached out to them and awaiting response.

Ah fantastic! Thanks for looking into this. Can confirm it's still an issue at my end.

hexcowboy · 2023-12-14T02:25:24Z

Hi everyone, I'm looking into this now. I think I found a bug in the LinkedIn OIDC implementation, I reached out to them and awaiting response.

is this in reference to this error message?

[auth][error] OperationProcessingError: "response" is not a conform Authorization Server Metadata response

because i'm also coming to the same conclusion

lovinzoop · 2023-12-19T11:57:02Z

SOLVED

After some debugging I managed to solve this. In case anyone else stumbles across this, since it's not well documented:
If you're using Linkedin API V2, you do need to add some custom parameters to the Linkedin provider. The original issue was that the expected iss was undefined. Simply add issuer to OAuthConfig for the Linkedin provider:
issuer: 'https://www.linkedin.com'
This triggers a new error: 'jwks_uri must be configured on the issuer'. Add jwks_endpoint to OAuthConfig:
jwks_endpoint: 'https://www.linkedin.com/oauth/openid/jwks'
Again, this triggers a new error, where nextauth complains that the profile id is missing. Linkedin API V2 use "sub" not "id". Solved by overriding the profile function in OAuthConfig:
             return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email,
                    image: profile.picture,
                }
            }
Complete working provider for Linkedin using Linkedin API V2:
LinkedIn({
            clientId: process.env.LINKEDIN_ID,
            clientSecret: process.env.LINKEDIN_SECRET,
            authorization: { params: { scope: 'profile email openid' } },
            issuer: 'https://www.linkedin.com',
            jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
            async profile(profile) {
                return {
                    id: profile.sub,
                    name: profile.name,
                    firstname: profile.given_name,
                    lastname: profile.family_name,
                    email: profile.email
                }
            },
        })
God bless, this is the right solution and docs should be updated

I tried this exact same configuration in LinkedInProvider, but I am not getting user information.

In the signIn callback, console the response

It's not giving any error, but I want user info like email, name etc
I am using next-auth 4.22.3

deibyrios · 2024-02-18T23:19:14Z

@alxwest not really. I’m not sure if @balazsorban44 is still working with LinkedIn for a fix. The other option option would be for someone to work on the conform() method but that’s beyond my current knowledge so, I guess we will have to dig into the issue and hack around Auth.JS to work, even with LinkedIn not being OIDC spec compliant.

cocoBavan · 2024-02-28T11:52:10Z

Putting logs inside node module files and patching things, I managed to get this far.

LinkedInProvider({
      clientId: process.env.LINKEDIN_CLIENT_ID,
      clientSecret: process.env.LINKEDIN_CLIENT_SECRET,
      authorization: {
        url: "https://www.linkedin.com/oauth/v2/authorization",
        params: { scope: "profile email openid" },
      },
      token: {
        url: "https://www.linkedin.com/oauth/v2/accessToken",
      },
      userinfo: {
        url: "https://api.linkedin.com/v2/userinfo",
      },
    })

But, it fails with the Error: TODO: Handle OIDC response body error. So, I believe the token returned is not correct and needs to fixed by Linked In?

Shashwat61 · 2024-03-01T03:09:59Z

Putting logs inside node module files and patching things, I managed to get this far.
LinkedInProvider({
      clientId: process.env.LINKEDIN_CLIENT_ID,
      clientSecret: process.env.LINKEDIN_CLIENT_SECRET,
      authorization: {
        url: "https://www.linkedin.com/oauth/v2/authorization",
        params: { scope: "profile email openid" },
      },
      token: {
        url: "https://www.linkedin.com/oauth/v2/accessToken",
      },
      userinfo: {
        url: "https://api.linkedin.com/v2/userinfo",
      },
    })
But, it fails with the Error: TODO: Handle OIDC response body error. So, I believe the token returned is not correct and needs to fixed by Linked In?

stuck at this point too

paschalidi · 2024-03-05T02:32:37Z

This has worked for me

export const authOptions: AuthOptions = {
 .
 .
 providers: [
    LinkedInProvider({
      clientId: process.env.LINKEDIN_CLIENT_ID!,
      clientSecret: process.env.LINKEDIN_CLIENT_SECRET!,
      client: { token_endpoint_auth_method: 'client_secret_post' },
      authorization: {
        url: 'https://www.linkedin.com/oauth/v2/authorization',
        params: { scope: 'openid profile email' }
      },
      wellKnown:
        'https://www.linkedin.com/oauth/.well-known/openid-configuration',
      issuer: 'https://www.linkedin.com',
      jwks_endpoint: 'https://www.linkedin.com/oauth/openid/jwks',
      async profile(profile: LinkedInProfile) {
        return {
          id: profile.sub,
          name: `${profile.given_name} ${profile.family_name}`,
          email: profile.email
        };
      }
    }),
  ]
 . 
 .

With auth scopes

And my application is not verified yet

cocoBavan · 2024-03-05T06:19:05Z

This has worked for me
And my application is not verified yet

@paschalidi I tried with those settings. Still doesn't work. May be you created this app a few months back? Could you please post the Products page? Mine looks like this.

paschalidi · 2024-03-05T13:00:49Z

I only created it yesterday.

cocoBavan · 2024-03-05T23:21:24Z

@paschalidi Good for you. I even created a new one and tried it. Still the same error. Maybe the version of the next Auth or some other libraries has something to do with it?

som-nitjsr · 2024-03-07T18:33:37Z

check the latest code LinkedIn openid connect implementation. currently, there are not support the code_verfier parameter and claim dose not return noce.
by setting these two parameter shoud work.

options.UsePkce = false;
options.ProtocolValidator.RequireNonce = false;

paramaggarwal · 2024-03-09T02:26:47Z

@balazsorban44 I understand that auto discovery does not work as of today due to the mismatch in issuer and wellKnown from LinkedIn's side. But we should be able to bypass discovery and manually configure the endpoints in the default LinkedIn config of the library.

authorization: {
  url: "https://www.linkedin.com/oauth/v2/authorization",
  params: { scope: "openid profile email" },
},
token: {
  url: "https://www.linkedin.com/oauth/v2/accessToken",
},
userinfo: {
  url: "https://api.linkedin.com/v2/userinfo",
},

This should have worked. But @cocoBavan and @Shashwat61 and myself are all stuck at this stage with error:

Error: TODO: Handle OIDC response body error
error {
   error: 'invalid_client',
   error_description: 'Client authentication failed'
}
GET /api/auth/callback/linkedin?code=(code) 302 in 522ms
... POST https://www.linkedin.com/oauth/v2/accessToken 401 in 479ms

On checking the details of the request for /v2/accessToken, I can see that there is a field code_verifier going which when removed the API call works successfully.

As mentioned by @som-nitjsr, this code_verifier parameter is not supported, but it is not clear how to disable PKCE.

balazsmeszegeto · 2024-03-27T10:45:24Z

check the latest code LinkedIn openid connect implementation. currently, there are not support the code_verfier parameter and claim dose not return noce. by setting these two parameter shoud work.
options.UsePkce = false;
options.ProtocolValidator.RequireNonce = false;

@som-nitjsr Where did you get this from? It is correct, just asking for the source

som-nitjsr · 2024-03-27T14:55:17Z

check the latest code LinkedIn openid connect implementation. currently, there are not support the code_verfier parameter and claim dose not return noce. by setting these two parameter shoud work.
options.UsePkce = false;
options.ProtocolValidator.RequireNonce = false;
@som-nitjsr Where did you get this from? It is correct, just asking for the source

I have used c# .net core and this is how i have integrated.

let me know which framework you are uisng
.AddOpenIdConnect("LinkedIn", "LinkedIn", options =>
{

 options.Authority = "https://www.linkedin.com/oauth/";
 options.CallbackPath = "/signin-linkedin";
 options.ClientId = "clinetid";
 options.ClientSecret = "code";
 options.ResponseType = "code";
 options.Scope.Add("openid");
 options.Scope.Add("profile");
 options.Scope.Add("email");
 options.ProtocolValidator.RequireNonce = false;
 options.Events = new OpenIdConnectEvents
 {
     OnAuthorizationCodeReceived = async context =>
     {
         // Remove the 'code_verifier' parameter
         context.TokenEndpointRequest.Parameters.Remove("code_verifier");
         await Task.CompletedTask;
     }
 };

});

som-nitjsr · 2024-03-27T15:15:07Z

also you can refer the c# code here where linkedin is connected uisng idp https://github.com/som-nitjsr/linkedidp

balazsmeszegeto · 2024-03-27T16:48:11Z

I am using ASP.NET Core, but couldn't figure out why PKCE would result in invalid_client error on token endpoint. Searching for the solution is how I ended up here and wanted to confirm, that it does indeed solve the issue.

check the latest code LinkedIn openid connect implementation. currently, there are not support the code_verfier parameter and claim dose not return noce. by setting these two parameter shoud work.
options.UsePkce = false;
options.ProtocolValidator.RequireNonce = false;

Furthermore, when you said: "check the latest code LinkedIn openid connect implementation" - I had the impression is that you're referring to an official or other publicly available implementation, so that's why I was asking for the source (the origin). Do you have that or did you figure this out on your own?

som-nitjsr · 2024-03-27T16:56:56Z

@balazsmeszegeto
i tested the token endpoint by passing the different parameters and figured out that code_verifer is not supported.

you can also see that they dont support nonce claim from here https://www.linkedin.com/oauth/.well-known/openid-configuration?_l=en_US

based on these i have written a solution here https://github.com/som-nitjsr/linkedidp

balazsmeszegeto · 2024-03-27T20:15:12Z

Great job then!

Still, I'd consider this as a bug in LinkedIn side, since nonce is mandatory as per OpenID C standard, and not an optional claim

pranavmappoli · 2024-04-13T11:32:21Z

Anyone find the final solution, still facing same error

kafiln · 2024-04-15T23:43:35Z

Anyone with a workaround for this ?

AbdelrahmanSadat · 2024-04-18T20:33:46Z

In case anyone comes across it, I had the same workaround in my codebase, until a different but similar error started showing:
https://next-auth.js.org/errors#oauth_callback_error unexpected iss value, expected https://www.linkedin.com, got: https://www.linkedin.com/oauth

I set issuer: 'https://www.linkedin.com/oauth' in the LinkedInProvider instead of issuer: 'https://www.linkedin.com', and the error is resolved.

mfts · 2024-04-21T05:28:24Z

I set issuer: 'https://www.linkedin.com/oauth' in the LinkedInProvider instead of issuer: 'https://www.linkedin.com', and the error is resolved.

I can confirm this also worked for me. Must be a recent change in the API.

balazsorban44 · 2024-04-21T07:15:12Z

Oh, it certainly is, I haven't gotten back a confirmation from them, but been asking for this for a while. Will fix it soon, now!

ndom91 · 2024-04-21T16:23:29Z

Put up a PR with the issuer update: #10671

wowtah · 2024-04-22T18:24:43Z

Did anybody get LinkedIn working for NextAuth.js v5?

With my current code, I get the LinkedIn login page, and a LinkedIn page where I press 'Allow' (this also shows it will redirect to localhost). After choosing Allow, my browser (now on http://localhost:3000/api/auth/error?error=Configuration) shows:

Server error
There is a problem with the server configuration.
Check the server logs for more information.

My logging shows:

GET /api/auth/signin 200 in 9ms
 POST /api/auth/signin/linkedin 302 in 32ms
error {
  error: 'invalid_client',
  error_description: 'Client authentication failed'
}
[auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
[auth][cause]: Error: TODO: Handle OIDC response body error
    at handleOAuth (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/lib/actions/callback/oauth/callback.js:86:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Module.callback (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/lib/actions/callback/index.js:32:41)
    at async AuthInternal (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/lib/index.js:39:24)
    at async Auth (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/index.js:126:34)
    at async C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:53191
    at async e_.execute (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:44492)
    at async e_.handle (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:54445)
    at async doRender (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1377:42)
    at async cacheEntry.responseCache.get.routeKind (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1587:40)
    at async DevServer.renderToResponseWithComponentsImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1507:28)
    at async DevServer.renderPageComponent (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1924:24)
    at async DevServer.renderToResponseImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1962:32)
    at async DevServer.pipeImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:920:25)
    at async NextNodeServer.handleCatchallRenderRequest (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\next-server.js:272:17)
    at async DevServer.handleRequestImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:816:17)
    at async C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\dev\next-dev-server.js:339:20
    at async Span.traceAsyncFn (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\trace\trace.js:154:20)
    at async DevServer.handleRequest (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\dev\next-dev-server.js:336:24)
    at async invokeRender (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\router-server.js:174:21)
    at async handleRequest (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\router-server.js:353:24)
    at async requestHandlerImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\router-server.js:377:13)
    at async Server.requestListener (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\start-server.js:141:13)
[auth][details]: {
  "provider": "linkedin"
}
 GET /api/auth/callback/linkedin?code=AQQzoxG4FredactedzW8aWageredactedYYmUsHXW3FsgQ9NbredactedwbF8D-TNbs_rdIbCbredactednZ_Dgy2RCZUBUYynredacteddICqBDJNBJhqUtFDDUWCEopZ-oypAH4gni5gN_PRnzmbh1OGgJP8NoxnUnhcAltC0oYz4_f5nA5ipY 302 in 319ms
 GET /api/auth/error?error=Configuration 500 in 12ms

I tried many variants of this code, some resulting in different errors. But still havent seen it working.

LinkedInProvider({
        clientId: process.env.LINKEDIN_CLIENT_ID!,
        clientSecret: process.env.LINKEDIN_CLIENT_SECRET!,
        client: { token_endpoint_auth_method: 'client_secret_post',  },
        authorization: {
          url: 'https://www.linkedin.com/oauth/v2/authorization',
          params: { scope: 'openid profile email' }
        },
        token: {
          url: 'https://www.linkedin.com/oauth/v2/accessToken',
        },
        wellKnown:
          'https://www.linkedin.com/oauth/.well-known/openid-configuration',
          userinfo: {
            url: 'https://api.linkedin.com/v2/userinfo',
            params: {
              projection: ``,
            },
          },
        issuer: 'https://www.linkedin.com/oauth',
        jwks_endpoint: 'https://www.linkedin.com/oauth/openid/jwks',
                
        profile(profile: LinkedInProfile) {
          return {
            id: profile.sub,
            firstName: profile.given_name,
            lastName: profile.family_name,
            email: profile.email,
            image: profile.picture,
          };
        },
        allowDangerousEmailAccountLinking: true
     
    })

I got it working for GitHub, so I am confident that my base setup is correct.
The versions I am using:

"@auth/core": "^0.30.0",
"@auth/prisma-adapter": "^2.0.0",
"next": "^14.2.2",
"next-auth": "^5.0.0-beta.16",

I am posting this here since this thread seems very relevant. Any help is appreciated :)

kafiln · 2024-04-22T18:48:02Z

Did anybody got LinkedIn working for NextAuth.js v5?

With my current code, I get the LinkedIn login page, and a LinkedIn page where I press 'Allow' (this also shows it will redirect to localhost). After choosing Allow, my browser (now on http://localhost:3000/api/auth/error?error=Configuration) shows:

Server error There is a problem with the server configuration. Check the server logs for more information.

My logging shows:

GET /api/auth/signin 200 in 9ms
 POST /api/auth/signin/linkedin 302 in 32ms
error {
  error: 'invalid_client',
  error_description: 'Client authentication failed'
}
[auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
[auth][cause]: Error: TODO: Handle OIDC response body error
    at handleOAuth (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/lib/actions/callback/oauth/callback.js:86:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Module.callback (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/lib/actions/callback/index.js:32:41)
    at async AuthInternal (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/lib/index.js:39:24)
    at async Auth (webpack-internal:///(rsc)/./node_modules/next-auth/node_modules/@auth/core/index.js:126:34)
    at async C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:53191
    at async e_.execute (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:44492)
    at async e_.handle (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:54445)
    at async doRender (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1377:42)
    at async cacheEntry.responseCache.get.routeKind (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1587:40)
    at async DevServer.renderToResponseWithComponentsImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1507:28)
    at async DevServer.renderPageComponent (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1924:24)
    at async DevServer.renderToResponseImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:1962:32)
    at async DevServer.pipeImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:920:25)
    at async NextNodeServer.handleCatchallRenderRequest (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\next-server.js:272:17)
    at async DevServer.handleRequestImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\base-server.js:816:17)
    at async C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\dev\next-dev-server.js:339:20
    at async Span.traceAsyncFn (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\trace\trace.js:154:20)
    at async DevServer.handleRequest (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\dev\next-dev-server.js:336:24)
    at async invokeRender (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\router-server.js:174:21)
    at async handleRequest (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\router-server.js:353:24)
    at async requestHandlerImpl (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\router-server.js:377:13)
    at async Server.requestListener (C:\Users\Wouter\source\repos\nxt14\node_modules\next\dist\server\lib\start-server.js:141:13)
[auth][details]: {
  "provider": "linkedin"
}
 GET /api/auth/callback/linkedin?code=AQQzoxG4FredactedzW8aWageredactedYYmUsHXW3FsgQ9NbredactedwbF8D-TNbs_rdIbCbredactednZ_Dgy2RCZUBUYynredacteddICqBDJNBJhqUtFDDUWCEopZ-oypAH4gni5gN_PRnzmbh1OGgJP8NoxnUnhcAltC0oYz4_f5nA5ipY 302 in 319ms
 GET /api/auth/error?error=Configuration 500 in 12ms

I tried many variants of this code, some resulting in different errors. But still havent seen it working.

LinkedInProvider({
        clientId: process.env.LINKEDIN_CLIENT_ID!,
        clientSecret: process.env.LINKEDIN_CLIENT_SECRET!,
        client: { token_endpoint_auth_method: 'client_secret_post',  },
        authorization: {
          url: 'https://www.linkedin.com/oauth/v2/authorization',
          params: { scope: 'openid profile email' }
        },
        token: {
          url: 'https://www.linkedin.com/oauth/v2/accessToken',
        },
        wellKnown:
          'https://www.linkedin.com/oauth/.well-known/openid-configuration',
          userinfo: {
            url: 'https://api.linkedin.com/v2/userinfo',
            params: {
              projection: ``,
            },
          },
        issuer: 'https://www.linkedin.com/oauth',
        jwks_endpoint: 'https://www.linkedin.com/oauth/openid/jwks',
                
        profile(profile: LinkedInProfile) {
          return {
            id: profile.sub,
            firstName: profile.given_name,
            lastName: profile.family_name,
            email: profile.email,
            image: profile.picture,
          };
        },
        allowDangerousEmailAccountLinking: true
     
    })

I got it working for GitHub, so I am confident that my base setup is correct. The versions I am using:

"@auth/core": "^0.30.0",
"@auth/prisma-adapter": "^2.0.0",
"next": "^14.2.2",
"next-auth": "^5.0.0-beta.16",

I am posting this here since this thread seems very relevant. Any help is appreciated :)

I am in the exact same situation.

Starefossen · 2024-04-29T14:39:06Z

Same configuration as @kafiln and @wowtah with the following error after callback from LinkedIn:

 POST /api/auth/signin/linkedin 302 in 24ms                                                                                       error {                                                          
  error: 'invalid_client',                                                                                                          error_description: 'Client authentication failed'
}                                                                                                                                 [auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
[auth][cause]: Error: TODO: Handle OIDC response body error

Config:

export const config = {
  providers: [
    GitHub({
      clientId: process.env.AUTH_GITHUB_ID,
      clientSecret: process.env.AUTH_GITHUB_SECRET,
      authorization: { params: { scope: 'openid profile email' } },
    }),
    LinkedIn({
      clientId: process.env.AUTH_LINKEDIN_ID!,
      clientSecret: process.env.AUTH_LINKEDIN_SECRET!,
      authorization: {
        url: 'https://www.linkedin.com/oauth/v2/authorization',
        params: { scope: 'openid profile email' }
      },
      issuer: "https://www.linkedin.com/oauth",
   })
  ]
}

GitHub auth works as expected.

Ranjanlc · 2024-05-01T01:49:25Z

Still facing this issue. Am I doing something wrong? As there are lots of solutions in this thread, still unsure what is the correct one. This is my LinkedIn provider and I have latest version of next-auth 4.24.7

And this is my linkedIn provider config:

    LinkedInProvider({
        clientId: process.env.LINKEDIN_CLIENT_ID || "",
        clientSecret: process.env.LINKEDIN_CLIENT_SECRET || "",
        client: { token_endpoint_auth_method: "client_secret_post" },
        authorization: {
          url: "https://www.linkedin.com/oauth/v2/authorization",
          params: { scope: "openid profile email" },
        },
        token: {
          url: "https://www.linkedin.com/oauth/v2/accessToken",
        },
        userinfo: {
          url: "https://api.linkedin.com/v2/userinfo",
        },
        wellKnown:
          "https://www.linkedin.com/oauth/.well-known/openid-configuration",
        issuer: "https://www.linkedin.com/oauth",
        jwks_endpoint: "https://www.linkedin.com/oauth/openid/jwks",
        profile(profile) {
          const defaultImage =
            "https://cdn-icons-png.flaticon.com/512/174/174857.png";
          return {
            id: profile.sub,
            name: profile.name,
            email: profile.email,
            image: profile.picture ?? defaultImage,
          };
        },
      }),

ERROR:

[next-auth][error][OAUTH_CALLBACK_ERROR] 
https://next-auth.js.org/errors#oauth_callback_error id_token detected in the response, you must use client.callback() instead of client.oauthCallback() {
  error: RPError: id_token detected in the response, you must use client.callback() instead of client.oauthCallback() 
      at Client.oauthCallback (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\openid-client\lib\client.js:632:15)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async oAuthCallback (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next-auth\core\lib\oauth\callback.js:111:16)
      at async Object.callback (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next-auth\core\routes\callback.js:52:11)
      at async AuthHandler (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next-auth\core\index.js:208:28)
      at async NextAuthApiHandler (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next-auth\next\index.js:22:19)
      at async K (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\compiled\next-server\pages-api.runtime.dev.js:21:2946)
      at async U.render (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\compiled\next-server\pages-api.runtime.dev.js:21:3827)
      at async DevServer.runApi (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\server\next-server.js:554:9)
      at async NextNodeServer.handleCatchallRenderRequest (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\server\next-server.js:266:37)
      at async DevServer.handleRequestImpl (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\server\base-server.js:789:17)
      at async C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\server\dev\next-dev-server.js:331:20
      at async Span.traceAsyncFn (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\trace\trace.js:151:20)
      at async DevServer.handleRequest (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\server\dev\next-dev-server.js:328:24)
      at async invokeRender (C:\Users\Lenovo\Documents\new.ontourism.academy\node_modules\next\dist\server\lib\router-server.js:174:21) {
    name: 'OAuthCallbackError',
    code: undefined
  },
  providerId: 'linkedin',
  message: 'id_token detected in the response, you must use client.callback() instead of client.oauthCallback()'      
}

holgerflick · 2024-05-03T03:24:59Z

I am also still getting an error:

[auth][error] OperationProcessingError: "response" is not a conform Authorization Server Metadata response
    at Module.processDiscoveryResponse (webpack-internal:///(rsc)/./node_modules/oauth4webapi/build/index.js:287:15)
    at getAuthorizationUrl (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/actions/signin/authorization-url.js:25:68)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Module.signIn (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/actions/signin/index.js:16:56)
    at async AuthInternal (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/index.js:72:24)
    at async Auth (webpack-internal:///(rsc)/./node_modules/@auth/core/index.js:126:34)
    at async /Users/holger/web/next.providers/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:53446
    at async e_.execute (/Users/holger/web/next.providers/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:44747)
    at async e_.handle (/Users/holger/web/next.providers/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:54700)
    at async doRender (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:1377:42)
    at async cacheEntry.responseCache.get.routeKind (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:1587:40)
    at async DevServer.renderToResponseWithComponentsImpl (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:1507:28)
    at async DevServer.renderPageComponent (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:1924:24)
    at async DevServer.renderToResponseImpl (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:1962:32)
    at async DevServer.pipeImpl (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:920:25)
    at async NextNodeServer.handleCatchallRenderRequest (/Users/holger/web/next.providers/node_modules/next/dist/server/next-server.js:272:17)
    at async DevServer.handleRequestImpl (/Users/holger/web/next.providers/node_modules/next/dist/server/base-server.js:816:17)
    at async /Users/holger/web/next.providers/node_modules/next/dist/server/dev/next-dev-server.js:339:20
    at async Span.traceAsyncFn (/Users/holger/web/next.providers/node_modules/next/dist/trace/trace.js:154:20)
    at async DevServer.handleRequest (/Users/holger/web/next.providers/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
    at async invokeRender (/Users/holger/web/next.providers/node_modules/next/dist/server/lib/router-server.js:174:21)
    at async handleRequest (/Users/holger/web/next.providers/node_modules/next/dist/server/lib/router-server.js:353:24)
    at async requestHandlerImpl (/Users/holger/web/next.providers/node_modules/next/dist/server/lib/router-server.js:377:13)
    at async Server.requestListener (/Users/holger/web/next.providers/node_modules/next/dist/server/lib/start-server.js:141:13)
 POST /api/auth/signin/linkedin 302 in 172ms
 GET /api/auth/error?error=Configuration 500 in 5ms

andersengenolsen added bug Something isn't working triage Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime. labels Oct 10, 2023

andersengenolsen closed this as completed Oct 11, 2023

andersengenolsen reopened this Oct 20, 2023

goerlitz mentioned this issue Oct 22, 2023

Sign In with LinkedIn is deprecated, use Sign In with LinkedIn using OpenID Connect instead #8316

Closed

goerlitz mentioned this issue Oct 25, 2023

LinkedIn Provider does not work for LinkedIn apps created since Aug 2023 (in V4) #8956

Closed

balazsorban44 added providers and removed triage Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime. labels Dec 12, 2023

meczajkowski mentioned this issue Mar 24, 2024

feat: linkedin auth - add config nerdbord/good-dev-hunting-app#264

Draft

ndom91 mentioned this issue Apr 21, 2024

fix(providers): update linkedin oidc issuer #10671

Merged

3 tasks

ndom91 closed this as completed in #10671 Apr 26, 2024

balazsorban44 mentioned this issue Apr 29, 2024

fix: strip code_verifier from request body when the provider doesn't support PKCE #10765

Merged

Auth provider for Linkedin not working #8831

Auth provider for Linkedin not working #8831

Comments

andersengenolsen commented Oct 10, 2023 • edited

Environment

Reproduction URL

Describe the issue

How to reproduce

andersengenolsen commented Oct 11, 2023 • edited

SOLVED

Complete working provider for Linkedin using Linkedin API V2:

goerlitz commented Oct 20, 2023

Deprecated API:

New API

andersengenolsen commented Oct 20, 2023 • edited

goerlitz commented Oct 20, 2023

jormaj commented Oct 20, 2023

andersengenolsen commented Oct 20, 2023

jormaj commented Oct 20, 2023 • edited

goerlitz commented Oct 20, 2023

bholagabbar commented Oct 20, 2023

SOLVED

Complete working provider for Linkedin using Linkedin API V2:

mehul1011 commented Oct 22, 2023

andersengenolsen commented Oct 22, 2023 • edited

mehul1011 commented Oct 22, 2023

GustavoContreiras commented Nov 6, 2023 • edited

AnatoleT commented Nov 8, 2023

benjamindell commented Nov 9, 2023

AmitSahoo45 commented Nov 30, 2023

goerlitz commented Dec 1, 2023

AmitSahoo45 commented Dec 2, 2023

balazsorban44 commented Dec 12, 2023

benjamindell commented Dec 12, 2023

hexcowboy commented Dec 14, 2023

lovinzoop commented Dec 19, 2023 • edited

SOLVED

Complete working provider for Linkedin using Linkedin API V2:

deibyrios commented Feb 18, 2024

cocoBavan commented Feb 28, 2024 • edited

Shashwat61 commented Mar 1, 2024

paschalidi commented Mar 5, 2024 • edited

cocoBavan commented Mar 5, 2024

paschalidi commented Mar 5, 2024

cocoBavan commented Mar 5, 2024

som-nitjsr commented Mar 7, 2024

paramaggarwal commented Mar 9, 2024 • edited

balazsmeszegeto commented Mar 27, 2024

som-nitjsr commented Mar 27, 2024

som-nitjsr commented Mar 27, 2024

balazsmeszegeto commented Mar 27, 2024

som-nitjsr commented Mar 27, 2024

balazsmeszegeto commented Mar 27, 2024

pranavmappoli commented Apr 13, 2024 • edited

kafiln commented Apr 15, 2024

AbdelrahmanSadat commented Apr 18, 2024 • edited

mfts commented Apr 21, 2024 • edited

balazsorban44 commented Apr 21, 2024

ndom91 commented Apr 21, 2024 • edited

wowtah commented Apr 22, 2024 • edited

kafiln commented Apr 22, 2024

Starefossen commented Apr 29, 2024 • edited

Ranjanlc commented May 1, 2024 • edited

holgerflick commented May 3, 2024

andersengenolsen commented Oct 10, 2023 •

edited

andersengenolsen commented Oct 11, 2023 •

edited

andersengenolsen commented Oct 20, 2023 •

edited

jormaj commented Oct 20, 2023 •

edited

andersengenolsen commented Oct 22, 2023 •

edited

GustavoContreiras commented Nov 6, 2023 •

edited

lovinzoop commented Dec 19, 2023 •

edited

cocoBavan commented Feb 28, 2024 •

edited

paschalidi commented Mar 5, 2024 •

edited

paramaggarwal commented Mar 9, 2024 •

edited

pranavmappoli commented Apr 13, 2024 •

edited

AbdelrahmanSadat commented Apr 18, 2024 •

edited

mfts commented Apr 21, 2024 •

edited

ndom91 commented Apr 21, 2024 •

edited

wowtah commented Apr 22, 2024 •

edited

Starefossen commented Apr 29, 2024 •

edited

Ranjanlc commented May 1, 2024 •

edited