400 Bad Request Error When Trying To Authenticate EBusiness Access Through OAM11gR2
(Doc ID 1639261.1)
Last updated on SEPTEMBER 10, 2018
Applies to:Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
OAM11gR2 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 substantal number are having the issue. Issue seen on all browsers
http trace sample -
Authorization: Negotiate YIIezwY(trimed for readablity)
HTTP/1.1 400 Bad Request
Date: Fri, 21 Mar 2014 00:51:14 GMT
Content-Type: text/html; charset=iso-8859-1
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