The number of failed login attempts works as not expected in OC 5.0.1

Last updated on DECEMBER 19, 2016

Applies to:

Symptoms

Oracle Clinical Users have encountered the unexpected behavior of the FAILED_LOGIN_ATTEMPTS
parameter, different from what's described in the OC Admin Guide Release 5.0.1.

In the Guide, it says if you set the FAILED_LOGIN_ATTEMPTS parameter to 6, you can expect that 3 wrong login
attempts would result in the account lock. It states:

--
Note:
In Oracle Clinical and RDC Onsite, the default Failed Login Attempts setting
of 10 is effectively 5. This is because Oracle Clinical uses proxy
connections and tries the internal connection twice for each user attempt
before locking the account due to an incorrect password.
--

The behavior for OC login attempts is now not as described above. For example, The FAILED_LOGIN_ATTEMPTS
parameter set to 6, after the seventh failed attempt (six previous failures) the account locks.

For RDC, it worked as documented in the Admin Guide i.e. FAILED_LOGIN_ATTEMPTS parameter
to 6, after the fourth failed attempt (three previous failures) the account locks.

Cause