I have a similar issue. I can, however, only reproduce it in a prod environment by giving it a valid username but a wrong non-empty password.