Noticed in AH4 Blazor demo that calling UpdateUserAsync when changing customers sets AspNetUsers.EmailConfirmed to 0, which prevents a subsequent login. Not good! I recommend using a ChangeTracker or accept an array of column names. Workaround currently is to do a manual update in the database.
Noticed in AH4 Blazor demo that calling
UpdateUserAsync
when changing customers setsAspNetUsers.EmailConfirmed
to 0, which prevents a subsequent login. Not good! I recommend using aChangeTracker
or accept an array of column names. Workaround currently is to do a manual update in the database.