Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
customfield_11100 18648
-
EPAM-Veg Sprint 1, EPAM-Veg Sprint 2, EPAM-Veg Sprint 3, EPAM-Veg Sprint 7
-
2
-
Vega
Description
As a person responsible for the security of the Folio platform
I want to prevent brute force attacks of the Folio platform when a user attempts to log in to Folio and fails.
Requirement
- Apply to user logging in with local username/password
- After the 3rd failed login attempt then display a message on Folio login screen [You have entered the wrong username or password for the third time. You have two more tries to login before your account will be locked.
- After 5 failed consecutive login attempts then lock user's Folio account and display a message on Folio login screen [For security, purposes, your account has been locked. Please contact your Folio System Administrator to reset your password.]
- To unlock an account, Folio administrator must change the user status = active on the User's record.
Screenshot
Acceptance Criteria
Given I am attempting to login to Folio
When I fail three times to login
Then the following message should display on the Folio login screen [You have entered the wrong username or password for the third time. You have two more tries to login before your account will be locked.]
Given I am attempting to login to Folio
When I failed 5 consecutive times to login
Then a message should display For security purposes, your account has been locked. Please contact your Folio System Administrator to reset your password.
Give my Folio account is locked
When I attempt to login again
Then the following message displays For security purposes, your account has been locked. Please try again or contact your Folio System Administrator.
Given a Folio user account is locked
When the Folio system administrator resets the user status = active on that user account
The user should be able to attempt to login to Folio
TestRail: Results
Attachments
Issue Links
- clones
-
UIU-591 Frontend: Indicate on User Detail record that the User is inactive due to failed login attempts
-
- Closed
-
- has to be done after
-
MODLOGIN-103 Backend: Security: Handling Failed login attempts via Folio Login Screen - Lock Account
-
- Closed
-
- is blocked by
-
MODLOGIN-86 Create/Extend password storage to support retaining last 10 changed passwords a user has saved
-
- Closed
-
-
MODLOGIN-89 Fix user blocking
-
- Closed
-
-
MODUSERS-101 SPIKE - Determine the approach for updating user record in an anonymous request
-
- Closed
-
-
RMB-320 Updating records containing metadata causes exceptions in database trigger
-
- Closed
-
- is cloned by
-
MODLOGIN-54 Show notification on the login page when a user account is blocked.
-
- Closed
-
- relates to
-
MODLOGIN-41 Backend - Security: Handling: Failed login attempts - Lock Account
-
- Closed
-
-
MODLOGIN-42 Security: Counting Failed login attempts
-
- Closed
-
-
UXPROD-39 Local password management
-
- Closed
-
- requires
-
RMB-353 Metadata without user id
-
- Closed
-