OAM 12.2.1.3.0 HTTP 400 Bad Request Accessing Protected Resource When Using OAM Identity Assertion Header
(Doc ID 2395270.1)
Last updated on JANUARY 08, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to use the OAM identity asserter in a WLS 12.2.1.3.0 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. A Java stack similar to the following may be observed in the managed server system output (nohup output from the server startup or the $DOMAIN_HOME/servers/<server name>/logs/<server name>.out file) when the issue occurs:
Changes
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 |