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
If you enable the user audit trail events and then attempt to sign in but type the wrong password you'll notice that three events are recorded:
A user updated event (the AccessFailedCount was incremented)
A login failed event that includes the user ID
A duplicate login failed event that does not include the user ID
Within the AccountController.Login method you can see that the LoggingInFailedAsync handler fires twice if the user is found (or just once if the user was not found).
Orchard Core version
1.8.3
To Reproduce
See above.
Expected behavior
The LoggingInFailedAsync handler should fire once and the audit trail event should be recorded once (with the user ID included).
The text was updated successfully, but these errors were encountered:
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).
This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.
Describe the bug
If you enable the user audit trail events and then attempt to sign in but type the wrong password you'll notice that three events are recorded:
Within the AccountController.Login method you can see that the LoggingInFailedAsync handler fires twice if the user is found (or just once if the user was not found).
Orchard Core version
1.8.3
To Reproduce
See above.
Expected behavior
The LoggingInFailedAsync handler should fire once and the audit trail event should be recorded once (with the user ID included).
The text was updated successfully, but these errors were encountered: