When migrating from auth0, why is it recommended to map the supertokens user id in my db?
I ll use the exported json method and in the frontend I ll keep using the auth0 id. (for old users only)
Also, when calling backend functions such as
getUserById
, siince I override them, I would anyway have to look in the json every time.
Am I missing something?
r
rp_st
06/24/2022, 12:15 PM
If you have the JSON then you can just use that and not store in the db
c
constantinos
06/24/2022, 12:22 PM
Do I need to set this to false?
> // Box 7: Set the newly created flag value to false in the response
> response.createdNewUser = false
I am thinking I should skip the whole condition (Box 5-7) ?
yea i mean you still have to map the supertokens user ID to the auth0 user ID right? Otherwise the userIds of the existing users will all change to the supertokens' user ID and then you have to migrate your application's tables accordingly
rp_st
06/24/2022, 12:27 PM
you should set createdNewUser field as well - just cause maybe you read this somewhere else and then that logic shouldn't break
SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).