Is it possible to have both Passwordless and EmailPassword recipies initialised at the same time on the backend? We want to serve 2 different apps (same top level domain). One frontend uses passwordless, the other uses email+password
06/20/2022, 11:14 AM
Yea! this is totally possible! You can do it, and it should just work.
06/20/2022, 11:20 AM
Ok I will give it a try.. I am looking to migrate users over to super tokens, but I dont want to have to force all users through a password reset flow. So step 1 is to silently create new users on supertokens every time a user succesfully logs in using the current auth system. Is it possible to just create a user, set a password, and have nothing emailed out to the user?
Then after a month of doing this I can switch over and users can just then login using the existing password
06/20/2022, 12:49 PM
> just create a user, set a password, and have nothing emailed out to the user?
Yes. By default, this happens.
06/22/2022, 3:37 PM
So the backend should call password.signup?
06/22/2022, 5:18 PM
The recipe you are using should have a signup function. You can use that. It will send no emails and won’t have any side effects