We’re doing a dry run for user data migration as we prepare to move to Auth0. However we found that in some cases, the email addresses from our registered users are not considered valid by Auth0 and rejected.
Specifically, we have found 2 patterns so far.
One pattern is if there are two or more consecutive periods in the email address. For example:
The other pattern is if there is a period right before the @ sign. For example:
I saw this issue here: Email validation for Auth0
I took the advice and created an input with the default HTML5 type email validator and tried the email addresses. The first case (foo…email@example.com) is NOT considered valid. However the second case (foo.@example.com) IS considered valid.
It’s kind of a big problem for us, because I don’t think we can ask customers to create a new email account just to have an address that Auth0 considers valid. Of course it’s partly our bad, for allowing people to register with a non-standards compliant email address. But it seems like Auth0 validator is also overly strict blocking some valid email addresses.
Any idea how to overcome this? We’ve already spent over a year preparing for the move to Auth0 to find out just now we’re blocked by this…