Supersedes#54287 I think.

Thank you@xabbuh.

@xabbuh this is a breaking change, earlier user checkers were not called for programmatic logins, now they're.

This has been working like this for a number of years and now the behaviour changed.

@faizanakram99 every bugfix breaks code that adapted itself to work with the bug. Defining a custom user checker implies that it replaces the default one but in this case the custom one was ignored, that is a bug.

just to comment that this properly addresses my original issue, calling the login user checker accordingly, thx@xabbuh and@chalasr

@faizanakram99 sad to hear that this break yours, can you detail your workflow of "security check" ? perhaps there is something different that may be done to satisfy both worlds

@94noni We were relying on the behaviour which was changed here and our tests broke all of sudden after upgrade, took me a while to figure this out. We adjusted it already with the new changes, thanks.