Nuno111 comments

Results 5 comments of


                                            Nuno111

Google Provider TODO: Handle OIDC response body error

Getting the same issue here. I've got the same setup for github and google, github works fine but google gives me the invalid_client error and cause HANDLE OIDC response body...

Google Provider TODO: Handle OIDC response body error

Sure thing @ndom91 Here's some screenshots with info auth.ts callbacks has some logic, but when using google it doens't even reach the callbacks, for github all works fine, thats why...

Google Provider TODO: Handle OIDC response body error

Didn't fix it for me, same issue unfortunately!

Google Provider TODO: Handle OIDC response body error

@ndom91 I dug a little deeper and it seems the codeGrantResponse is not authorized before making the proccesAuthorizationCodeOpenIDResponse function call,

Google Provider TODO: Handle OIDC response body error

@ndom91 @murilobd Bumping to .17 solved my issue. I then ran into another problem which you can find here https://github.com/nextauthjs/next-auth/issues/9922 But basically i changed my NEXTAUTH_URL to NEXTAUTH_URL_INTERNAL and now...