Oblogintrycount Always Lock Account When Exceed 100 even when policys are not defined
Last updated on AUGUST 11, 2015
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms