OIM/OAM: Xelsysadm Resets A User's Password, Password Is Changed In LDAP, But User Cannot Login
Last updated on NOVEMBER 20, 2017
Applies to:Identity Manager - Version 184.108.40.206.0 to 220.127.116.11.3 [Release 11g]
Information in this document applies to any platform.
OIM 18.104.22.168/OAM 22.214.171.124 integration setup (with Ldapsync enabled)
The user cannot login with a new password after being locked out after 3 invalid attempts.
It was noticed that in LDAP (odsee 11g), some attributes such as oblockouttime and oblogintrycount are not zeroed after xelsysadm resets a user's (atest10) password:
Workaround: xelsysadm has to do additional workaround of lock and unlock user, this is not acceptable.
User locked out after 3 failed login attempts, but does not automatically unlock.
Even after running "Automatically Unlock Users"
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