Details
-
Bug
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
4.3.1, 7.5.0
-
None
-
-
CP: sprint 127
-
1
-
Core: Platform
-
GBV
Description
Steps to Reproduce:
- Don't use (delete) the mod-login configuration options that reside in mod-configuration:
- login.fail.attempts
- login.fail.timeout
- login.fail.to.warn.attempts
- Log into some FOLIO environment as any user
- The login succeeds.
Expected Results:
No error message in the logs.
Actual Results:
These errors in the log
ERROR LoginAttemptsHelper No config found by code login.fail.attempts ERROR LoginAttemptsHelper No config found by code login.fail.timeout ERROR LoginAttemptsHelper No config found by code login.fail.to.warn.attempts
Information:
When the config option is missing the default values are used. This is documented in the README: https://github.com/folio-org/mod-login/blob/v7.5.0/README.md#module-properties-to-set-up-at-mod-configuration
TODO:
Suppress any ERROR and WARN messages in the log if the missing config option results in using the default value. An INFO message is fine.
TestRail: Results
Attachments
Issue Links
- relates to
-
MODLOGIN-41 Backend - Security: Handling: Failed login attempts - Lock Account
-
- Closed
-
-
MODLOGIN-42 Security: Counting Failed login attempts
-
- Closed
-
-
MODLOGIN-181 500 returned when login.fail.to.warn.attempts isn't configured & login fails more than once
-
- Closed
-