In production my app send "Invalid_client" when I try to sign in even after double-checking the .env variable

[D2Mat]

Hi,

I deploy on vercel my app configure with nexth-auth and Linkedin auth0.

Everything was working well in dev mode, but not in production.

This is why I double check all the .env var. It seems that everything is ok.

I check the authorization from LinkedIn and everything looks great.

To replicate you can sign in here

Log from the vercel Lambda function

[GET] /api/auth/callback/linkedin?code=<-----token----->

17:59:46:22

2021-03-25T16:59:46.460Z	2022a902-6758-4be1-a6fa-77878c5a8387	

ERROR	[next-auth][error][oauth_get_access_token_error] https://next-auth.js.org/errors#oauth_get_access_token_error {  statusCode: 401,  data: '{"error":"invalid_client","error_description":"Client authentication failed"}'} undefined undefined2021-03-25T16:59:46.461Z	2022a902-6758-4be1-a6fa-77878c5a8387	

ERROR	[next-auth][error][oauth_get_access_token_error] https://next-auth.js.org/errors#oauth_get_access_token_error {  statusCode: 401,  data: '{"error":"invalid_client","error_description":"Client authentication failed"}'} linkedin <-------here_token------>	

ERROR	[next-auth][error][oauth_callback_error] https://next-auth.js.org/errors#oauth_callback_error {  statusCode: 401,  data: '{"error":"invalid_client","error_description":"Client authentication failed"}'}

I can't understand where does the error come from. Your help will be very much appreciated ?

Have a good day !

[balazsorban44]

have you checked if you allowed the callback url correctly on your Auth0 dashboard?

[D2Mat]

I have done that. But I am not sure if the function logs in vercel will display full debug logs. Thanks for your precious time @balazsorban44

[balazsorban44]

Not sure either. But if you are only interested in the production logs, build your project locally, and start a production server on localhost:3000 with npm start

[D2Mat]

So as you advise me, I build on localhost. Everything worked well there, but when I deploy on vercel it kept on crashing with this error :

[next-auth][debug][oauth_callback_protection] Comparing received and expected state {  state: '724f6fc673023a2ec109fc5c8c07e5503be99f8712dcd0cfab1bb67807ac88ec',  expectedState: '724f6fc673023a2ec109fc5c8c07e5503be99f8712dcd0cfab1bb67807ac88ec'}2021-03-26T09:39:24.316Z	f7498bfb-0054-423f-8911-b9c79ebf45bb	

ERROR	[next-auth][error][oauth_get_access_token_error] https://next-auth.js.org/errors#oauth_get_access_token_error {  statusCode: 401,  data: '{"error":"invalid_client","error_description":"Client authentication failed"}'} undefined undefined2021-03-26T09:39:24.317Z	f7498bfb-0054-423f-8911-b9c79ebf45bb	

ERROR	[next-auth][error][oauth_get_access_token_error] https://next-auth.js.org/errors#oauth_get_access_token_error {  statusCode: 401,  data: '{"error":"invalid_client","error_description":"Client authentication failed"}'} linkedin <----token---->2021-03-26T09:39:24.317Z	f7498bfb-0054-423f-8911-b9c79ebf45bb	

ERROR	[next-auth][error][oauth_callback_error] https://next-auth.js.org/errors#oauth_callback_error {  statusCode: 401,  data: '{"error":"invalid_client","error_description":"Client authentication failed"}'}

[D2Mat]

@balazsorban44 Error fixed ! I am so happy 💯.

What I did :

• reset all the environment variables in Vercel
• double check them
• redeploy in production

This was not such a big deal after all but just discipline

Have a good day 😃

[balazsorban44]

Awesome!