I deleted the google-auth provider account, but now when I tried to change the email account from fakename@hotmmail to fakename@hotmail.com I get an error
It seems after you delete a user account, auth0 still remembers the email and therefore blocks you from added the account again. So now I have to tell my customer: sorry, I can’t fix this. You can’t use our service anymore.
If you have a google social account for fakename@hotmail.com you should still be able to create an email/password account for that same address. Uniqueness does not apply here.
Yup, I agree, it doesn’t sound right to me either, which is why I’m reporting it.
I just sent you a PM with some screenshots. I’m happy to jump on a video chat if you want to see for yourself. If I have this user submit a GDPR request, will that ensure you really delete their information? It seems you must be doing a “soft delete” or else you have an indexing issue.
Did you check the link I referenced? I’m not the first to report this. And it seems like you guys closed it unresolved back them.
I cannot … create a user with some email (that existed before, but was subsequently deleted), neither via API nor via the website. If I try, I get the message “The user already exists.”
I don’t think we are doing a “soft delete”. I created a user with an email, changed it to something else and then created a new user with the original email, no issues there.
Can you run an export users job (or use the extension), and search the resulting file for that email address?
I have this same issue. No user returned via dashboard or API for example@gmail.com, but when trying to update user with email - example2@yahoo.com to example@gmail.com, I get error message - ‘Error! The specified new email already exists’
Just seen this. Just one more datapoint – this is still an issue for us, too. We use a workaround (instead of bulk deleting/creating a bunch of users in rapid succession, we introduced artificial timeouts between the calls to Auth0 API. We also hope the issue doesn’t manifest itself IRL…
One more reason to avoid Auth0 in future projects, I’m afraid…