Lock Counter Gets Incremented by 2 and Audit Logging of Login Activity is Logged Twice With Wrong Password And Use Of Tab Button
(Doc ID 2698107.1)
Last updated on MAY 12, 2022
Applies to:
Oracle Banking Digital Experience - Version 18.1.0.0.0 to 18.1.0.0.0 [Release 18]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When user tried to login by having entered correct username and incorrect password by pressing tab button to proceed each step and click enter on login button two issues are observed -
- Lock counter issue in Users Table (counter increases by 2 instead of 1)
- Twice Login activity is unnecessarily coming in digx_audit_logging
In case of user inputting correct username and Password and proceeding using tab button, login is successful but two rows in digx_audit_logging is observed
EXPECTED BEHAVIOR
-----------------------
When using tab and entering correct username and incorrect password - lock counter should increase by 1 and digx_audit_logging should be incremented by 1 row with login activity - FAILED.
In case of user inputting correct username and Password - digx_audit_logging should be incremented by 1 row with login activity - SUCCESS.
STEPS
-----------------------
1. Hit the OBDX (Oracle Banking Digital Experience) Netbanking page.
2. Enter correct username and incorrect password but use tab to navigate to each field and click enter on submit.
3. Observe the lock_counter in USERS table and DIGX_AUDIT_LOGGING table.
4. Enter correct username and incorrect password but use tab to navigate to each field and click enter on submit.
5. Observe DIGX_AUDIT_LOGGING entries
Changes
No changes done to the product account or hardware causes this issue. This is caused purely by user action while login.
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 |
Changes |
Cause |
Solution |
References |