How do I implement permanently disabled (lockout) feature, so that user can't log in, in ASP.NET core 2 identity

Question

0.00/5 (No votes)

See more:

, +

Well, after a few hours of googling, I still can't find an answer, not even partial one. Is this even possible, or it must be custom solution?

What I have tried:

I've played around with locked out feature of Identity, but it seems, that is not the answer, because in that scenario user is locked out for a fixed amount of time, not indefinitely.

Posted 5-Nov-18 3:08am

1suli0

Updated 5-Nov-18 4:23am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

MadMyche · Accepted Answer · 2018-11-05T04:23:00

Welcome to the club of people looking for permanently disabling a user.

We have used different versions of Identity going back about a decade, the method we ended up with was going custom; adding a AccountLocked [bit] field to the db schema.
We do have an Admin interface to manage all of the users, so this method was not too hard to add in. It also would be easy to set the Lockout Time to some really far into the future date as well.

The NuGet package has a recent discussion on this; and it appears that this method is what they are considering for the future:
What is considered best practice for disabling / deactivating users? · Issue #1858[^]