My Oracle Support Banner

Oblogintrycount Always Lock Account When Exceed 100 even when policys are not defined (Doc ID 2040172.1)

Last updated on JULY 05, 2018

Applies to:

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

Symptoms

OID is used as datastore/userstore in OAM-OIM integrated environment. Password policy is disabled in OID and OIM.

In oam-config.xml Lockout and defaultretrylimit=0
Auth Scheme used is LDAPScheme that contain - OverrideRetryLimit=0

Though no lockout setting, Account get locked (on OAM) after 100 invalid password. Account is not locked in OID or OIM but just in OAM.

This is because of obLockedOn getting updated when oblogintrycount reaches 100.

Every login with invalid password the counter get increased. But it always shows account locked when hit 100. If keep retry with invalid pass, counter will be increased 101,102, 103 etc.

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
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.