2 ms·
There does exist a legitimate (though contrived) use case for not telling the user which of the fields is wrong: when a user misspells their username and that m
by kibwen 12y ago
There does exist a legitimate (though contrived) use case for not telling the user which of the fields is wrong: when a user misspells their username and that misspelled username belongs to another user. From the user's point of view the username would be wrong but the password would be right, whereas from the site's perspective this is reversed and would produce an incorrect error message. This particular case would be particularly insidious because it's impossible to review a password after typing it.
Like I said, contrived, but security-by-obfuscation isn't necessarily the sole motivation (though likely the commonest).