the login fails (because of an incorrect password) and
login.fail.to.warn.attempts is not configured and
login attempts do exist
...mod-login returns a 500 error
This occurred when using an edge API & the password within FOLIO was not the same password stored for the API key 'user'.
Steps to Reproduce:
- Cause an edge API call to fail by using an incorrect password within FOLIO (for the user connected to the API key) or by setting up the wrong password for the 'api user' outside of FOLIO.
- Login attempts should exist in the DB...so you may have to make the API call a 2nd time.
- login.fail.to.warn.attempts should not be configured.
'Password does match for userid....' error should be recorded in the log and the appropriate http code returned.
http 500/internal server error is returned.
Exception recorded in the log.
This occurred in a Juniper environment. I have not tested it in kiwi.
If previous login attempts do not exist, the password error is logged and mod-login returns a 422/Unprocessable Entity: