My Oracle Support Banner

Oracle Access Manager (OAM) When Trying To Access A Protected Resource Gets "Failed to lead resource" In Trace "HTTP-400 Bad Request" (Doc ID 2725723.1)

Last updated on NOVEMBER 03, 2020

Applies to:

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

Symptoms

Oracle Access Manager (OAM) When Trying To Access A Protected Resource Gets "Failed to lead resource" In Trace "HTTP-400 Bad Request"

Scenario

When trying to access the protected resource, user notice HTTP 400 (Bad Request) error in HTTP Trace for one of the URL that browser tries to load. Main protected URL worked alright and partial page loads. Header variable like user name from OAM is visible.

 

Steps to reproduce

1. Access OAM protected application URL, that causes HTTP 400 error



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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.