Last updated on SEPTEMBER 10, 2016
Applies to:Oracle Application Object Library - Version 188.8.131.52 to 184.108.40.206 [Release 11.5]
Information in this document applies to any platform.
***Checked for relevance on 26-Nov-2012***
***Checked for relevance on 26 Jul 2013***
***Checked for relevance on 02 Feb 2015***
***Checked for relevance on 10 Sep 2016***
Users can continue to attempt to login continually even if the "Signon Password Failure Limit" profile option is set. The end date for the user does not become end dated and there is no indication in the Users form (FNDSCAUS.fmb) that the user account is locked.
Run this SQL to verify if the user is locked:
SELECT DECODE (encrypted_user_password
, 'INVALID', 'Account locked'
, 'Account not locked')
WHERE user_name = '&username';
If the encrypted_user_password is invalid then the user the account is locked.
Steps to reproduce:
Create a user, assign a password, assign responsibilities.
Set the Signon Password Failure Limit profile option e.g. 5.
Login to applications as the user and follow the prompts for resetting the password.
Login again using an incorrect password and receive the following error message:
"Login failed. Please verify your login information or contact the system administator."
Continue attempting to login using an incorrect password for 5 times.
The error still appears and the FNDSCAUS form shows that user is not end dated.
The user can still login using the correct password.
Applied ATG PF CU2 <patch:4125550> or <patch:4083215>.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms