I use the asp.net identifier, and I have several custom classes that inherit from IdentityUser.
Suppose I have an inheritance chain like:
IdentityUser <- AppUser <- ServiceUser <- ServiceEmployee and ServiceCustomer (which both inherit from ServiceUser).
When trying to create a single login form as a better strategy?
If you use the OTB account controller and change the UserManager to use ServiceUser, but try to log in to the account registered as ServiceEmployee, it will not work, because FindAsync (), apparently, tries to find only based on "ServiceEmployee" in the discriminator field therefore, if the account has been registered as another "type", it cannot be used to log in. Thus, this happens with any combination when different types of registered and input types are different.
Should I update the login action to use multiple UserManager so that there is a check for each type of user or is there a better way to do what I'm trying to achieve.
Thanks for any info.