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?

Hey @nabb23 we actually had docs for this a while back but removed them cause export users is just way easier

ThirdPartyEmailPassword

check this out: https://github.com/supertokens/docs/blob/612a456bc3ce2708718cdd17b13467ec664ca42a/v2/thirdpartyemailpassword/migration/from-auth0/account-migration/modifications-to-login.mdx

Thanks! Will take a look and come back if any questions

Sounds good

This was really helpful - one thing thats missing is verifying the email and skipping the email verification, seems to be possible? https://supertokens.com/docs/thirdpartyemailpassword/migration/account-creation/email-verification I've tried chaining straight into the signin function like so:

if (legacyLoginResult.status === 'success') {
    await this.emailPasswordSignUp(input);
    return originalImplementation.emailPasswordSignIn(input);
}

you don't really need to call the signIn function after callling signUp.

Is there a readily available function for that in the sdk? Or need to make the http calls?

There is a function for that

Got it working - did not expect to be able to call the recipe directly from within the other one but it works! thanks again