My Oracle Support Banner

Why Doesn't WebGate Pass REMOTE_USER To Backend JBoss Application? (Doc ID 1917283.1)

Last updated on MARCH 08, 2017

Applies to:

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

Goal

An application has been integrated with Oracle Access Manager (OAM) SSO with the following components:


When an OAM-protected JBoss application resource is accessed via the Apache webserver, after OAM SSO login the application fails to display the page because it does not find REMOTE_USER variable available in the HTTP request.

If the following is added to the Apache configuration then REMOTE_USER is set and application access is successful:

RequestHeader set REMOTE_USER %{REMOTE_USER}s
Header add REMOTE_USER %{REMOTE_USER}s


Why is this Apache configuration required?

Why isn't WebGate passing the REMOTE_USER value to the back end JBoss Application Server?

Solution

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
Goal
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.