Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My straight forward attempt is here to check the password validity after the login succeeded against the backend. Only in that case we certainly know, who the users is (not just the loginname) and can be certain that the password used to be right. This avoids that information is leaked to the outside (user enumeration? chance for social engineering?), although it comes at costs, that already postLogin events were done by other apps (for instance, the lastLogin timestamp is already set).
We could act in the BeforeUserLoggedInEvent event, with the constraints named above, and need guessing over the user id (we have mechanisms). I tend to change it thereto.