OAM HTTP 400 Bad Request Accessing Protected Resource When Using OAM Identity Assertion Header

(Doc ID 2395270.1)

Last updated on MAY 08, 2018

Applies to:

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


When attempting to use the OAM identity asserter in a WLS environment using the OAM Identity Assertion header, any attempt to access a resource on the WLS server results in an HTTP 400 "Bad Request" Response.




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