My Oracle Support Banner

Oracle Access Manager (OAM) OAMconsole - Account Lockout Not Working With Embeddled LDAP As System Store (Doc ID 2701277.1)

Last updated on DECEMBER 23, 2021

Applies to:

Oracle Access Manager - Version 12.2.1.3.191201.0123.S and later
Information in this document applies to any platform.

Symptoms

The OAMconsole "Account Lockout" does not work for the Embeddled LDAP as the System Store

Steps to reproduce:

1. In Weblogic Admin Console, add a test user account <TEST_ADMIN_USER> and assign it to the Administrator group.

2. Configure the Session Lockout in Weblogic Admin Console.

a. Navigate t0 Security Realms -> <REALM_NAME> -> Configuration -> User Lockout.

b. Change Lockout Threshold to: 5

3. Login to the WL Admin Console using account <TEST_ADMIN_USER> and enter the incorrect password 5 times, the lockout is enforced

4. Login to the /oamconsole using that same account <TEST_ADMIN_USER> and enter the incorrect password 5 times, the lockout is not enforced

 

 

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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