We’ve been using Passwordless login (on a Hosted Page/Universal Login) for a few months now and have decided to implement an embedded login form our-side via auth0.js, to provide both Passwordless and Database (e-mail/password) login options to our users.
This question is related to the solution mentioned here:
But instead of removing our Passwordless login, we’d wish to keep both. I understand we can use the Import/Export extension to get a list of Passwordless users and import them to our Database connection (worked fine in our staging tenant) - however, this doesn’t solve the situation for future users who decide to
login via a magic link in the future. If a user decides to do that, then in order to gain access via a password they’d have to perform an independent sign up and link their accounts, correct?
Is there an easy way to keep all users’ e-mails linked (we also provide Google and Slack logins) across auth providers? So that when a user has already logged in via Google’s OAuth, they could send themselves a password reset link (as opposed to going through the sign up flow)? I’m guessing the Management API will come into play and we’d have to ourselves hook into every signup and walk through our existing users to find if the e-mail doesn’t already exist in the Database with a password and if not, enter the user’s e-mail into it?