My Oracle Support Banner

If User Name Length Is Greater Than 10, Transaction Is Not Getting Locked Even After Max Failed Attempts Exceeds (Doc ID 2447804.1)

Last updated on SEPTEMBER 18, 2019

Applies to:

Oracle Banking Digital Experience - Version 18.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

OTP enabled transactions are not getting locked even after user crossed maximum allowed failed attempt. This is happening if User Name length is more than 10.

Simulation Steps:
-----------------------
The issue can be reproduced with the following steps:
1> log in with admin user.
2> From authentication, enable OTP for any transaction, say for Internal transfer.
3> Log in with a retail user whose username length is more than 10.
4> Do internal transfer. On confirm button click OTP verification screen enable.
5> Input wrong OTP and done all available attempts.
6> On 0 attempts will get an error as "System cannot process the request currently. Please try later." Also, the transaction not getting locked.


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.