400 Bad Request Error When Trying To Authenticate EBusiness Access Through OAM11gR2 (Doc ID 1639261.1)

Last updated on APRIL 21, 2017

Applies to:

Oracle Access Manager - Version 11.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

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 -

GET /oam/CredCollectServlet/WNA?authn_try_count=0&spnegotoken=string
Authorization: Negotiate YIIezwY(trimed for readablity)


HTTP/1.1 400 Bad Request
Date: Fri, 21 Mar 2014 00:51:14 GMT
Server: Oracle-Application-Server-11g
Content-Length: 223
Connection: close
Content-Type: text/html; charset=iso-8859-1

Cause

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