lockout | Put your Laravel application into read-only mode | REST library

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

Yes

Under any of these 2 circumstances:

• UserManager is subclassed and the virtual bool SupportsUserLockout property is overridden and that implementation returns false.
• UserManager.Store (your IUserStore implementation) does not implement the optional IUserLockoutStore interface.

• If you're using the "stock" in-box ASP.NET Core Identity functionality, without using any custom IUserStore implementation (and without subclassing UserManager), then your runtime IUserStore will be some subclass of abstract class UserStoreBase<...> which does implement IUserLockoutStore.
  • e.g. ASP.NET Core Identity for Entity Framework uses Microsoft.AspNetCore.Identity.EntityFrameworkCore.UserOnlyStore which inherits the IUserLockoutStore interface implementation.
• Because in C#/.NET, interfaces are strictly additive (one cannot "remove" an interface from a class - you can only reimplement it) it means if you don't want to subclass UserManager then you will cannot use a subclass UserStoreBase<> as the basis for your reimplementation of IUserStore<> - you'll have to start from scratch, basically.
  • (Which in my mind, at least, means that ASP.NET Core Identity's default combination of UserManager and UserStoreBase<...> is a bad OOP design because it requires implementations to actively go through a lot of effort to correctly not support something, instead of making everything opt-in.
  • Hey kids, inheritance is bad, mmm'key (okay, not "bad", but at least is so fraught with problems it should be avoided.
    • Subclass inheritance is a blunt instrument, especially in C# and Java, where it's impossible to separate a type's "interface"1 from implementation, and can't describe a type's interface in a type algebraic way - so we can't define a class Derived that subclasses a parent class Base : ISomeInterface such that class Derived no longer implements ISomeInterface (the best we can do is either abuse implicit conversions to a separate type, or "hide" members with [EditorBrowsable] and reimplement the interface explicitly with throw new NotSupportedException(), which is horrible, but even Microsoft does it in some places in .NET's base libraries, such as in Stream and TextWriter subclasses).
    • (Also, don't (ab)use inheritance just to have "common members" in different types. I agree that it does suck that C#/.NET still doesn't support mixins, but the drudgery of copy+pasting forwarder properties and methods around is less painful in the long-term than dealing with the consequences of inappropriate use of inheritance.

1: By "interface" I don't mean interface types; I mean the set of public members of a class or struct, i.e. a type's exposed surface.

(In an earlier edit of my post, I suggested that IConfigureOptions could be used to configure SupportsUserLockout, however I was wrong: as there is no option to outright disable the lockout system, but if you were to subclass both LockoutOptions to add a bool Enabled property and subclass UserManager to specify override bool SupportsUserLockout to return LockoutOptions.Enabled (_{ideally, from an immutable copy, not the original mutable options object}) then that would work.

What you want to do is called "Asynchronus task processing" and needs some more things to it.

I would use bull as a framework to work with your Queue based on Redis. This will let you store a form submit request in a queue and process it in a new process and the user can close the connection after submitting the form.

In NodeJs it could look like

json_serializable will generate an implementation of fromJson, but it can't add a factory or static method to your class. You'll have to create the factory yourself (and let the generated implementation do all the real work):

You need to call PasswordSignInAsync first. If user requires Two Factor Authetnication special cookie will be set which will be used by GetTwoFactorAuthenticationUserAsync

After starting from ground zero, I feel I found the problem. I am now getting logon via Swagger API service (Angular 13) and the logon.cshtml Identity Razor scaffolding page.

When one properly adds the Identity scaffolding, one needs to change/review the IdentityHostingStartup.cs file. My updated IdentityHostingStartup is as follows:

Do not know the exact reason but changing the default authentication scheme worked for me.
In your startup.cs file, change
from this:

Overriding SigninManager and UserManager is a lot of work. There are so many things that needs to be implemented for it to work.

I tucked my tail and went back to default calls and with the AspNet*** tables in place, I got the data seeded and login works like a charm.

If it compiles, it is probably well-formed code. The compiler would issue an error message if the ternary operator could not be used with those operands on account of their type. The fact that there's no such error message suggests that there is no such problem with your code.

However, under some conditions, use of the ternary operator can result in possibly unintended copying.

If both the on and off methods return void (or, say, bool) there won't be any issue of copying, and the code will work as expected: if lockout[idx] is true then bulb[idx].off() will be evaluated, otherwise bulb[idx].on() will be evaluated. Only one of the two alternatives will be evaluated, just like what would happen with the if statement.

Generally, the ternary operator is used when you need the result to be an expression. Otherwise, writing the code using an if statement is usually more readable.

async void seems to be the problem here. It is not clear why you use that (async void) instead of returning an action result.

The framework does not wait for the request to be properly handled so by the time your code reaches the second call of your injected dependency, the action has gone out of scope since async void methods are invoked as fire and forget.

The controller action should return a relevant action result for the request

For example