Last updated on SEPTEMBER 28, 2016
Applies to:Oracle Access Manager - Version 18.104.22.168.0 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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms