Welcome to the Kinde community.

A
A
A
M
T

No organization set when using sign in with X/Twitter

It seems like when signing up/in with X (Twitter), the default organization is not set. I don't know if this is the cause but I also got a 500 error after trying to sign up. I could eventually sign in with it though but obviously it's not a good experience for users.
D
e
A
8 comments
Thanks for reporting, I will look into this
We have asked a few users to test the auth today and there was problems with all the providers (email, Apple, Google, X) atm actually. I can see that we did get a new Apple user, but an error page was still presented after the sign up (similar to the problem above).

It seems a bit hit and miss. In addition to the problem using X yesterday, another person on the team also had problems with Google.

So it seems like there would randomly be problems with either:
  1. Sign up fails and error page shows.
  2. Sign up succeeds and error page shows.
We will try to debug this a bit more as well but it seems a bit tricky since the errors don't show up every time.
Adding some error messages here if it helps.

Authentication flow: Received: null | Expected: State not found
Plain Text
… var/task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/oauth2-flows/AuthorizationCode.js in AuthorizationCode.<anonymous> at line 175:35
… var/task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/oauth2-flows/AuthorizationCode.js in step at line 47:23
… var/task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/oauth2-flows/AuthorizationCode.js in Object.next at line 28:53
… var/task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/oauth2-flows/AuthorizationCode.js in fulfilled at line 19:58
node:internal/process/task_queues in process.processTicksAndRejections at line 95:5


Cannot get user details, no authentication credential found
Plain Text
… /task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/clients/server/authorization-code.js in <anonymous> at line 159:31
… /task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/clients/server/authorization-code.js in step at line 43:23
… /task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/clients/server/authorization-code.js in Object.next at line 24:53
… /task/node_modules/@kinde-oss/kinde-typescript-sdk/dist/sdk/clients/server/authorization-code.js in fulfilled at line 15:58
node:internal/process/task_queues in process.processTicksAndRejections at line 95:5
Have you set up the Social Logins with your own credentials?
Sorry, not sure exactly what that means.
I will try to read more in the docs about this.
Oh yea I see what you mean now, thank you. I do vaguely remember setting up things like this from many years ago..
That's great actually since it's something we could fix. Thank you!

I'm curious why it worked for some of the auth attempts though?
Add a reply
Sign up and join the conversation on Discord
Join