400 Bad Request Error When Trying To Authenticate EBusiness Access Through Oracle Access Manager 11g R2PS2 (OAM 11.1.2.x)
(Doc ID 1639261.1)
Last updated on AUGUST 29, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Symptoms
Oracle Access Manager 11g R2PS2 (OAM 11.1.2.x) with WNA Authentication
OHS act as proxy for OAM Managed server port
Some users have a browser error page displayed when they try to authenticate using OAM. The page error is "400 Bad Request".
The content of the page is "Bad Request The request could not be understood by server due to malformed syntax".
This does not occur for all users, though a substantial number are having the issue. Issue seen on all browsers
http trace sample -
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 |
Cause |
Solution |
References |