I’ve got Auth0 almost completely set up now for our production environment, and I am trying to finish it off with hooking in the migration of existing users with a custom database. I’ve followed all the steps here so far: https://auth0.com/docs/connections/database/migrating.
When doing my testing using the “Try” button on the Login script, I see the calls going to my legacy server as expected. I’ve named my new DB “Legacy-Database-Users-Do-Not-Remove” and enabled my client to use it as a connection along with the default “Username-Password-Authentication” where I plan on making my net new users going forward.
I am now not clear how to actually login using my client. When I get to the lock screen, there is no way to select a legacy database, and if I put in a user that only exists in the legacy database I don’t see any calls occur, just an error saying that I have the wrong user.
Should I instead be changing my main “Username-Password-Authentication” database to be a “custom” database, so there is only one database, or do I need to customize the lock page to select which database to use? Are there pro/cons to each approach that I should be considering?
To be clear about my use case, I want users who exist in my current legacy database to be able to login using their existing password, which will then automatically put them into my default connection and they will never hit my legacy database again. I do not want to migrate users from one connection to another and force them to re-set their password.