I’m currently in the process of migrating our auth flow from something in house to auth0. Moving kind of slow, but I’m getting there!
This current problem I’m having is how to handle a not-yet-migrated user who tries to login via social sign ins?
As mentioned, our in house authentication flow is being migrated to auth0 via automatic migrations. It’s all working and good, but it only works if the user logs in via the regular email and password input in auth0’s Universal Login.
I’m trying to handle the scenario where a user, who has not been migrated, tries to login to their gmail via
Continue with Google which I noticed, so far, creates a google-connection user in User Management.
I found a way to prevent social sign ons via a rule, and I was in the middle of leveraging it to query the custom database first, then if the email exists, prevent the sign on. Alas, I noticed it still creates a user in auth0’s User Management.
Is there a way prevent the creation of a user if they sign on using a social connection should they exist in some custom database?