Signon Password Profile Settings Causing Users to Become Locked out of E-business After Unsuccessful Password Attempts
Last updated on JUNE 29, 2018
Applies to:Oracle Application Object Library - Version 12.1.3 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.
When a user has one or more unsuccessful logins to E-Business Suite followed by a successful login, the password failure count is not being reset to zero when the successful login occurs.
Steps to Reproduce:
1. Set the user's Signon Password Failed Attempts profile setting to 3.
2. The user logs attempts to login with two incorrect passwords.
3. During the third attempt the correct password is used.
4. User is able to login.
5. The user then logs out.
6. The user attempts to login again and using incorrect password on the first attempt.
7. On the second attempt the correct password is used.
8. User is locked out.
The following set of patches were applied to the environment;
20378476 - ORA-20001: FND_CANT_UPDATE_USER_ROLEHAS BEEN DETECTED INFND_USER_RESP_GROUPS_API
26543378 - ORACLE APPLICATION FRAMEWORK (FWK) RELEASE 12.2.6 BUNDLE 6
21624242 - APPLICATIONS R12 INTEROPERABILITY PATCH FOR JRE PLUGIN
26175708 - FND SECURITY RUP JUN-2017
25982922 - ORACLE APPLICATIONS RELEASE 12.2: CPU PATCH FOR JUL 2017
25678886 - Fix for Bug 25678886
25678887 - Fix for Bug 25678887
25678888 - Fix for Bug 25678888
23708596 - 12.2.5 CONSOLIDATED PATCH FOR JULY 2016 CPU FIXES FOR FRM
22376551 - Fix for Bug 22376551
23708283 - 12.2.5 CONSOLIDATED PATCH FOR JULY 2016 CPU FIXES FOR BNE
It has been reported that the Patch 27468058 - ORACLE APPLICATIONS RELEASE 12.2: CPU PATCH FOR APR 2018 also causes this issue.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms