Use GUID instead of email when email is username about brockallen.membershipreboot

[rodmjay]

so what you are saying is that there will always be a username, but in the case of EmailIsUsername it would be a guid, correct?

[brockallen]

I want to accommodate the "email is username" option but also allow for user's to change their email address. Currently when an account is created the username is just assigned from the email, so if at any point they change their email then the nameidentifier claim will have the old email which will look odd if/when the email is changed.

If we use a GUID (or something else like it) then what we'll have is a nameidentifier like tenant:guid, a email and name claims which match the current email.

The other change this entails is that when authenticating if the app has set the "email is username" option, then we'll have to load the account by email (not username). This is an internal detail, but I note it here for completeness.

This shouldn't break anything and shouldn't require any DB changes when upgrading (one the feature is done) as long as the app has been relying upon the nameidentifier claim for a unique ID for the account (or the int PK if you've been doing it at the DB level).

[brockallen]

I think this will assuage my concern: 943dc84