Oracle Access Manager 11gr2ps2 (OAM 11.1.2.2.0) Oblogintrycount is not Reset After Lockout Period/Duration (Doc ID 2268826.1)

Last updated on NOVEMBER 09, 2023

Applies to:

Symptoms

Oracle Access Manager 11gr2ps2 (OAM 11.1.2.2.0) Oblogintrycount is not Reset After Lockout Period/Duration

• The oblogintrycount value keeps incrementing after the lockout period has expired.
• In the test case, a user that has failed authentication 3 times and is locked out for 1 hour. This is working properly. We are expecting OAM to allow another 3 authentication attempts after the lockout period is over. However, after the lockout period is over, if the user attempts another bad authentication (while oblogintrycount still equals 3) the oblogintrycount is being incremented to 4 and the user is locked out for another hour (oblockouttime and oblastfailedlogin are updated).
• Our DCC authentication scheme is set to "OverrideRetryLimit=1" and our password policy contains max attempts=3 and lockout duration=60min.
• OAM version: 11.1.2.3.170418
• OS: Oracle Linux 6 (virtual) on Exalogic
• Webgate: 11.1.2.3.170418 on Apache 2.4.6 (Oracle Linux 7)
• DB: 12.1.0.2 on Exadata
• Directory: OUD - 11.1.2.3.170418
• OAM BUNDLE PATCH 11.1.2.3.170418

Changes

Cause

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