I still need to look into #1. I’ll get back to you in the next day or so.
For #2 there is an example where a short lived token is issued and the user is redirected to reset a password before finishing authentication. It’s in the doc I linked. If you need some help hashing this out further let me know where you are getting caught up and I can assist.
For #7 I am not positive as to why you can’t import a social connection, but I believe you cannot directly import and create social users because those users are authenticated by their specific IDP (FB, google, etc.). To work around this you would just import those users in a custom auth0 DB connection, and use account liking to link the account information when they log in with one of their social connections. Since account linking relies on similar emails to link accounts, it should be no problem to make sure their old data gets connected.
The flow would be something like this:
- You import those users to an auth0 custom db
- Set up automatic account linking. You can choose to link accounts with the same email and merge metadata.
- The user logs in via Google (or any social) with the email they had before the user migration
- The rule checks for that email in your custom auth0 DB, and if it exists the old account and the new social account are linked
I have seen this flow suggested as a solution.
Hope this helps.
Thanks,
Dan