Emails with Apostrophe or Single Qoute unable to reset-password

Help
, , ,
1

Submitted a ticket and also posting here as I believe it is in issue with the password reset widget:

When a user navigates to the reset-password flow from the email link provided. The user’s email is incorrect when submitting the form to reset password.

Current Behaviour:

  • User is navigated correctly to the ‘reset-password’ widget hosted by Auth0.
  • Widget displays users email address correctly: e.g someone.o’example@domain.com
  • Widget does not proceed when submitting new password and shows no errors.
  • Logs in Auth0 Tenant clearly show that the request failed. The email shown in the logs is stripped of special characters showing “someone.oexample@domain.com”.

Expected Behaviour:

  • User is navigated correctly to ‘reset-password’ widget hosted by Auth0.
  • Widget displays user email address correctly: e.g someone.o’example@domain.com
  • Widget proceeds to ‘success’ state when the ‘submit’ button is clicked.
  • Logs in Auth0 Tenant show the request succeeded. The email shown in the logs is as registered, displayed in reset-password email and as displayed in reset-password widget.
1 Like
2

Thanks for reporting that. Let’s see what our developer support engineering team has to share on that front in the ticket.

3

Paraphrase from support ticket response:

Auth0 Team have identified the issue. It looks like a particular field is holding the email and triggering the browser validation. Other recent tickets indicated issues have been encountered with the ‘&’ and ‘#’ symbol, and now appears the apostrophe/single quote also triggers this error. As these are all valid characters from providers in the local part of the email address, the intention is to fix the issue. A ticket has been added to the teams backlog but there is no ETA.

Workaround from Auth0
A workaround is to use the ‘New Universal Login’ template without any customisation.

My Tid bit
This isn’t a solve for our particular case as branding is important but hopefully this will allow others to work-around it in the interim.

1 Like
4

Thanks for following up on that and sharing it with the rest of community!