SessionData.getErrorCode=Invalid_User In Case Of Account Lockout In OAM\OAAM PS3 Environment
(Doc ID 2151306.1)
Last updated on FEBRUARY 01, 2019
Applies to:Oracle Adaptive Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
We have a OAM-OAAM integration environment.
Integration is using TAPScheme, we do have custom OAAM pages as part of oracle.oaam.extensions.war deployed on OAAM.
The password policies are enforced on OUD which is the user store for OAM, invalid login attempts is set to 5 and after which user would be forwarded to the lockout page based on the value of sessionData.getErrorCode=disabled.
However, OAAM server is printing sessionData.getErrorCode() = invalid_user even after user lockout.
The same use case returns sessionData.getErrorCode() = disabled in PS2 environment.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document