When does Identity's UserManager not support lockouts?

ASP.NET Core Identity has UserManager.SupportsUserLockout(), which for me is true.

Description:

Gets a flag indicating whether the backing user store supports user lock-outs.

MEDevel.com: Open-source for Healthcare and Education

Collecting and validating open-source software for healthcare, education, enterprise, development, medical imaging, medical records, and digital pathology.

Visit Medevel

Is it ever possible for the user manager NOT to support lockouts?

>Solution :

Is it ever possible for the user manager NOT to support lockouts?

Yes – when you’re implementing your own IUserManager instead of using the in-box implementation.

This can happen if you want to use ASP.NET Identity‘s public API as a front for an existing user account database and/or authentication system, e.g. LDAP/Active Directory where Group Policy is set to disable account lockouts, or some other user-accounts backend that doesn’t support lockouts, or some custom implementation where the project-manager has deemed lockouts an undesirable feature or not worth the development cost to implement.

Another case is when you’re configuring the in-box UserManager (which doesn’t implement IUserManager, curiously enough) in ConfigureServices via IConfigureOptions<IdentityOptions> and disable Lockout via LockoutOptions.