My Oracle Support Banner

Error "Persistence Exception Occurred" When User Is Not Locked Even After 3 Invalid Attempts For Self Boarded Retail User Having 2FA Enabled And Username Length More Than 10 Digits. (Doc ID 2827885.1)

Last updated on DECEMBER 14, 2021

Applies to:

Oracle Banking Digital Experience - Version to [Release 18]
Information in this document applies to any platform.


User is not locked even after 3 invalid attempts for self boarded retail user having username length more than 10 digits, following error is observed.

Persistence exception occurred

The issue can be reproduced at will with the following steps:
1. Login to OBDX.
2. Self-Onboard a retail user with username to be entered must have length more than 10 characters.
3. System will ask OTP.Try to enter wrong otp all 3 times.
4. At 3rd time of entering the OTP the system will throw the error as mentioned above.
5. After onboarding successfully , try to login with the same user.
6. Perform any payment transaction.
7. Enter invalid OTP for 3 times.
8. At third time of invalid OTP attempts, error is thrown as mentioned above.

PS:- 2FA is enabled for login and payment transactions.

The issue has the following business impact:
Due to this issue, OTP is not locked even after 3 invalid attempts


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

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