Retail User Not In Locked State Even If Wrong Credentials Are Submitted Multiple Times
(Doc ID 2723979.1)
Last updated on NOVEMBER 03, 2020
Applies to:
Oracle Banking Digital Experience - Version 19.2.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Retail user is not getting locked if the wrong credential is submitted multiple times. As in application lock counter is maintained to be 5 user must be locked after 5 invalid attempts.
But LOCK_COUNTER and LOCK_STATUS of user table are not getting updated either.
EXPECTED BEHAVIOR
-----------------------
User must be locked, if wrong credentials are put more than 5 times.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Go to login Portal.
2. Enter wrong Retail user username and password credentials.
3. Click on Submit.
4. Try wrong credentials for more than 5 time.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |