Question/suggestion for turning off a connection's "custom database"

[chris.olson]

https://auth0.com/docs/users/migrations/automatic

After reading the doc above, I had some questions/suggestions regarding custom database connections

1. The process for disabling “use my own database” could be much easier. Instead of copying a no-op return into each of the custom scripts, it would be ideal if the toggle for disabling “use my own database” actually worked and did this for us.

2. I’m very confused/curious about the statement “You will also want to keep Import Users to Auth0 (on the Settings page) enabled.” After setting no-op statements in the login/get_user scripts, why does the “import users to auth0” setting play any role in a user authenticating who’s credentials have already been imported to auth0’s data store? Indeed, turning off this option results in users unable to login, but the user’s credentials have already been migrated to auth0.

Thanks,
Chris

[chris.olson]

“bump”…is that allowed here?

[markd]

I don’t have answers … just adding some noise hoping this gets some attention. Great questions that I would like the answers to as well. I would have assumed the process for disabling custom DB user migration would be to just undo what you did to enable it.

[Woonz]

I have exactly the same questions. Could someone of Auth0 support please give an answer to this?

[James.Morrison]

Hey there everyone, let me see if I can find out some more information on this front. Thanks!

[James.Morrison]

@chris.olson

• The process for disabling “use my own database” could be much easier. Instead of copying a no-op return into each of the custom scripts, it would be ideal if the toggle for disabling “use my own database” actually worked and did this for us.
• I’m very confused/curious about the statement “You will also want to keep Import Users to Auth0 (on the Settings page) enabled.” After setting no-op statements in the login/get_user scripts, why does the “import users to auth0” setting play any role in a user authenticating who’s credentials have already been imported to auth0’s data store? Indeed, turning off this option results in users unable to login, but the user’s credentials have already been migrated to auth0.

After confirming with one of our senior support engineers, both of these points stated above are correct and the current path forward to get them resolved would leaving feedback at Auth0: Secure access for everyone. But not just anyone. as this gives us a direct pipeline to feedback and use-cases. Please let me know if you have any additional questions. Thanks!