OUD Proxy Is Not Properly Handling The "user Locked" Message Received From LDAP Backend
(Doc ID 2765451.1)
Last updated on MAY 17, 2023
Applies to:
Oracle Unified Directory - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
The incorrect Error code is displayed on Oracle Access Manager (OAM) login page when connecting to OUD Proxy as a backend server.
The OUD PROXY ForkJoin workflow is not displaying the additional information which is provided from the Microsoft AD Server regarding the authentication failure.
The client application displays the wrong messages to users regarding the authentication failure reason.
The below is the output from command line when using AD:
Changes
OUD-Proxy is configured with 2 AD backend server using Fork-Join.
OAM uses OUD-Proxy as backend idstore and getting incorrect error when user is locked/disabled.
OUD-Proxy ForkJoin does not return additional information of error even after 'return-bind-error-messages' is set to 'True' as per Doc ID 2109044.1
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |