Oracle Access Manager (OAM) Login Fails 400 Bad Request After Submitting Credentials (Doc ID 2474746.1)

Last updated on DECEMBER 24, 2024

Applies to:

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

Environment

Oracle Access Manager (OAM)

2 OAM Servers in a cluster, listening on SSL Port for <MANAGED_SERVER_PORT>

2 OHS Servers with WebGate. The 2 OHS Servers listen on <SSL_PORT>

mod_wl_ohs.conf (WLS Proxy Plugin) configured to forward /oam requests to the 2 OAM Servers in the cluster

1 Load Balancer in front of the 2 OHS Servers, listening on <SSL_PORT>

OAM Server host in Access Manager Settings set to LOAD BALANCER Host and <SSL_PORT>

Steps to reproduce

1. Access the protected URL via the Load Balancer: http://<LBR-HOSTNAME>.<DOMAIN>:<PORT>/<FILE_NAME>

2. User is redirected to OAM for authentication. However, the OOTB login page loses all formatting.

3. Fiddler Trace shows that all Javascripts, CSS and Images files throw a 400 (Bad Request error), as shown below:

	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

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