Best Practice - Logging In - Using email or username?

[admin85]

Hi Gerald,

Thanks for providing insight into the process(es) involved with changing a user’s email address!

I definitely want to avoid any possible issues that may arise from the user changing their email address. Ideally, I want to maintain the original account if possible as I’ll be using the Auth0 id (ClaimTypes.NameIdentifier ) value as key for any user-specific data being stored. I’m assuming this would change as well when a new account is created with the updated email?

I see Auth0 has a “username” option to use as their login versus the email address. I’m thinking that might be the only way to maintain the integrity of the original account while allowing the user to change their email. However, it appears John from this post is advising against using a “username” instead of an email as the login, but I’m not sure why…

Login identifier as either username or email

We currently are set up to utilize email as the login identifier and that works. We are expecting to roll out a new social component to our web app and would like to utilize the username field in order to not require users to make their email public. Is it possible to have the login page work with either email or username being typed into the identifier page: [image]

Just wanted to determine the best approach for maintaining the user’s Auth0 id (ClaimTypes.NameIdentifier ) at the time of creation while allowing them to update their email (or other related info) when needed.

Thanks,

Josh