Propagating lock status from OAM to OUD not working in an OAM-OIM integrated Env

(Doc ID 1668438.1)

Last updated on SEPTEMBER 28, 2016

Applies to:

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


"oblockedon" attribute is not set by OAM when the user is locked due to too many failed login attempts
Customer  manually added the OBLOCKEDON attribute to the user and ran the OIM LDAP recon and it worked


 Customer following test case in - Automatic Locking and Unlocking of the Users in OAM Integrated OIM Environment (Doc ID 1496808.1)


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