My application needs to handle two different types of user (lets call them Internal and External). Both could use the standard identity provided backed off to SQL Server, meaning that I can take advantage of the registration and password handling logic.
But, for External users, I need to collect more information at initial registration. I also need External users to have an email address as their User Id, rather than a simple string.
I could probably bludgeon in two instances of the standard provider, but that feels tricky and to a degree overkill in terms of duplication.
I then spotted that the table created in SQL Server has a "discriminator" column containing the text "ApplicationUser" for all the existing records. That suggests to me that I could use that column to drive different processing for the two user types.
However, there doesn't seem to be much (ok, any) documentation on doing that or ...
Go to the complete details ...