UserName and Email in Identity core

[codelovercc]

Thanks anyone who build and support this great project!
Why does username must be an email in Identity core default UI? UserName is user's name and it doesn't matter if it's a email or not. Since I don't want use the email as the UserName, I can't not log in with default Identity core UI.

I found this source code in Microsoft.AspNetCore.Identity.SignInManager<TUser>.PasswordSignInAsync

public virtual async Task<SignInResult> PasswordSignInAsync(
      string userName,
      string password,
      bool isPersistent,
      bool lockoutOnFailure)
    {
      TUser byNameAsync = await this.UserManager.FindByNameAsync(userName);
      return (object) byNameAsync == null ? SignInResult.Failed : await this.PasswordSignInAsync(byNameAsync, password, isPersistent, lockoutOnFailure);
    }

and about this line TUser byNameAsync = await this.UserManager.FindByNameAsync(userName); , I think it should call await this.UserManager.FindByEmailAsync(userEmail) because of the UI Login form shows a Email input tag. Other ways it should take normal UserName as login model, UserName can be any thing and it can be a email too.

[codelovercc]

Or it should be like this

public virtual async Task<SignInResult> PasswordSignInAsync(
      string userNameOrEmail,
      string password,
      bool isPersistent,
      bool lockoutOnFailure)
    {
      TUser byNameOrEmailAsync = IsEmail(userNameOrEmail) ? await this.UserManager.FindByEmailAsync(userNameOrEmail) : await this.UserManager.FindByNameAsync(userNameOrEmail);
      return (object) byNameOrEmail == null ? SignInResult.Failed : await this.PasswordSignInAsync(byNameOrEmail, password, isPersistent, lockoutOnFailure);
    }

Using FindByEmailAsync or FindByNameAsync to find a TUser.

[captainsafia]

Triage: The two are conflated for historical reasons. If you want the two to be separate, you'd have to produce a scaffold with username and email as separate fields.

I found this source code in Microsoft.AspNetCore.Identity.SignInManager.PasswordSignInAsync

To resolve this, you'd have to find the username by the email before invoking the PasswordSignInAsync. There's no API to do this currently.

Dupe of #44660

[ghost]

Hi @codelovercc. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.