Why Doesn't WebGate Pass REMOTE_USER To Backend JBoss Application?
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
COREid Access - Version 10.1.4.3.0 and later
Information in this document applies to any platform.
An application has been integrated with Oracle Access Manager (OAM) SSO with the following components:
- JBoss Application Server
- Apache 2.2 WebServer proxying requests for the JBoss Application Server
- OAM WebGate installed on Apache 2.2 Webserver
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:
Why is this Apache configuration required?
Why isn't WebGate passing the REMOTE_USER value to the back end JBoss Application Server?
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