I'm getting "Something went wrong. Please try again" when I try to login. Both social logins and email/pw give the same error. Is there anywhere I can get more information about what's wrong?

Hey guys, wanted to ask if there’s a way to host supertokens on aws? I have successfully hosted on local host for not but we would like to host it on Aws in the future

Hey folks - We're currently building out a migration away from cognito (which - does not allow user exports), so we need to do a slow migration towards supertokens. Current thinking is to use ThirdPartyEmailPassword.emailPasswordSignInPOST, and if the login with supertokens fails, try to login with the old auth provider. If this succeeds - we want to create the user in supertokens with their user/password, bypass email verification, etc. Havent been able to find in the docs thus far where we can pass the user/pass along for creation, mind pointing me in the right direction?

Hello, I was checking the server logs, and I found Token theft detected. What does this mean and more importantly how it is triggered ? at what scenario you throw this error ?

Is there any solution for e2e testing with Google login? Google blocks all UI attempts at logging in. I tried looking into their apis, but Supertokens is operating as the middle person, so I can't log in via Google's APIs. Has anyone found a non-mocked way of doing e2e testing with Google logins? I'm using Nightwatch (a node selenium based framework).

I am trying to create a websocket server & I need to authenticate the clients. I can authenticate them in rest apis , how can i do it using Socket.io with supertokens..

I occasionally get the error

No SuperTokens core available to query

. It fails my requests. I'm only on dev right now - hoping this doesn't happen on prod?

is there a way to list all users?

is there a way to embed a redirectToPath url argument during the email verification process?

I noticed that the Auth0 external id (

sub

) for the google provider was

google-oauth2|<ID>

. Now with supertokens I am building this within

createNewSession

, for mapping the accounts.

const externalUserId = user.thirdParty ? `${user.thirdParty.id}|${user.thirdParty.userId}` : null;

I noticed that

user.thirdParty.id

, here is

google

and not

google-oauth2

. Is it safe for me to simply replace the

google|

part with

google-oauth2

, is the

<ID>

part of the auth0 sub stable?