You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2018. It is now read-only.
I would define disabling / deactivating a user as having a property held against that user which prevented them from being able to log into the application when the property had been set to a certain value.
We are building an admin section where admin members can disable / re-enable users as required.
The options I have identified:
Set email confirmed to false. To re-activate a user, regenerate an email confirmation link for them.
Or
Set Lockout Enabled to True and Lockout End to DateTime.Max
Or
Add IsEnabled field to AspNetUsers (default to True) and override SignInManager to check value is True before returning a Success result.
Are there any other options / which is the most recommended?
The text was updated successfully, but these errors were encountered:
All of these should work, there was some effort around making it easy to do via SignInManager's CanSignIn method, so 3 is probably closest to how we envisioned something like this working, but the other two options seem reasonable as well.
I would define disabling / deactivating a user as having a property held against that user which prevented them from being able to log into the application when the property had been set to a certain value.
We are building an admin section where admin members can disable / re-enable users as required.
The options I have identified:
Or
Or
Are there any other options / which is the most recommended?
The text was updated successfully, but these errors were encountered: