NormalizedUserName VS Username in DotNet Core

asp.net-identity asp.net-core-mvc asp.net-core-identity
pedrommuller picture pedrommuller · Sep 23, 2016 · Viewed 12.8k times · Source

I'm trying to create a custom implementation of IUserLoginStore for MongoDB and I noticed when using 

UserManager<ApplicationUser>

with the method

 var userResult = await _userManager.CreateAsync(user);

it goes through the implementation of 

GetUserNameAsync
FindByNameAsync
SetNormalizedUserNameAsync
GetUserIdAsync

I would like to clarify two questions:

  • what's the purpose of having a NormalizedUsername and a UserName? the only difference that I could notice id that the normalizedUserName is in uppercase.

  • I'm using my Implementation only to store users from an external login(Google plus), is there a way that I can omit username and NormilizedUserName since basically, I'm using the email in these three fields, I'm feeling that I'm duplicating data and it doesn't make any sense to me.

any recommendations?

Answer

blowdart picture blowdart · Sep 23, 2016

1) Normalization stops people registering user names which only differ in letter casing.

2) No - those fields are part of the basic data model.

Related questions

How override ASP.NET Core Identity's password policy

By default, ASP.NET Core Identity's password policy require at least one special character, one uppercase letter, one number, ... How can I change this restrictions ? There is nothing about that in the documentation (https://docs.asp.net/en/latest/security/…

Read More
How to get the current logged in user Id in ASP.NET Core

I've done this before with MVC5 using User.Identity.GetUserId() but that doesn't seem to work here. The User.Identity doesnt have the GetUserId() method I am using Microsoft.AspNet.Identity

Read More
ASP.NET Core Identity - get current user

To get the currently logged in user in MVC5, all we had to do was: using Microsoft.AspNet.Identity; [Authorize] public IHttpActionResult DoSomething() { string currentUserId = User.Identity.GetUserId(); } Now, with ASP.NET Core I thought this should work, but it …

Read More