Users' Accounts not Getting Locked In OIM when locked via OAM
Last updated on MARCH 08, 2017
Applies to:Identity Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
**Checked for Relevance on 25-Jul-2014**
With Oracle Identity Manager (OIM) 11g integrated with OAM, OAAM, OID and OVD with LDAP-Sync, when a user tries to log in to an application protected by OAM through OAAM with an incorrect password 5 times, the user gets locked in OID. This is reflected by the oblogintrycount and oblockouttime attributes in OID, but the account remains unlocked in OIM, due to which, admins have to go into OID to unlock the user instead of using the OIM console. Why is the account not locked within OIM?
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