Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
customfield_11100 18646
-
EPAM Sprint 1, EPAM Sprint 2, EPAM Sprint 3, EPAM Sprint 4
-
5
-
Folijet
Description
As a person responsible for the security of the Folio platform
I want to prevent brute force attacks of the Folio platform
Conditions for Locking a Folio User Account
- At [5] failed consecutive login attempts using a Folio username/password then lock user's Folio account
- OR if [5] failed consecutive login attempts using Folio username/password occur in a [10 minute span] then lock user's Folio account
- Settings Configuration: the settings in [brackets] should be configurable as Folio may need to change these settings in the future.
- Settings Configuration: should be flexible to support additional rules for locking a user's Folio account
Potential way to lock a Folio User Account
- A way to lock the user's Folio account is by setting the user status = inactive
Ways to unlock a Folio User Account
- Via Folio, system librarian changes the user status = active
TestRail: Results
Attachments
Issue Links
- blocks
-
UIU-591 Frontend: Indicate on User Detail record that the User is inactive due to failed login attempts
-
- Closed
-
- clones
-
UIU-591 Frontend: Indicate on User Detail record that the User is inactive due to failed login attempts
-
- Closed
-
- relates to
-
MODLOGIN-54 Show notification on the login page when a user account is blocked.
-
- Closed
-
-
MODLOGIN-171 Logs ERROR when using default config values
-
- Closed
-
-
UIU-590 Frontend: Security: Handling Failed login attempts via Folio Login Screen - Lock Account
-
- Closed
-
-
UXPROD-39 Local password management
-
- Closed
-