Use Shibboleth environments variables in mod_proxy_http

[Cantor, Scott]

On 8/5/13 6:03 PM, "pradeepkumar" <gmpradeep at gmail.com> wrote:
>
>We are planning to switch from "mod_jk" to "mod_proxy_http"

Why would you do that? You should use mod_proxy_ajp in most cases, but
certainly not mod_proxy_http.

>and found that
>Shibboleth environment variables are not set even when we turned on
>"ShibUseEnvironment On" in "mod_proxy_http"

It's on by default, and in no case will such data show up on a proxied
HTTP server anyway, you can only proxy headers (or by creating headers
before proxying based on the environment).

>While testing, the Shibboleth-SP Environment attributes as well as
>REMOTE_USER are NOT available to the Tomcat-hosted J2ee application. In
>short, request.getRemoteUser() returns NULL and
>request.getAttribute("shibattr-email") returns NULL too.

And they always will. That's how HTTP proxying works.

>Please note that the values for the environment variables are coming fine
>with request attributes, if the "mod_jk" settings were used.

Which is why you should use it, or the modern version, proxy_ajp.

>Is that any limitation in using Shibboleth environment variables with
>"mod_proxy_http"

Has nothing to do with Shibboleth at all.

-- Scott