Set an attribute as REMOTE_USER but don't pass the attribute in the forwarded request

[Bradley Wagner]

Nate, that's a great tip. Thanks.

Scott, I understand that it has to be mapped so that it can be
referenced in REMOTE_USER, but I was wondering if it could then be
unset or suppressed from the forwarded request while the REMOTE_USER
was left. Basically, the attribute would only exist while the request
was being processed by mod_shib but not after.

I'm curious now what would happen if I don't set the "AJP_" prefix. I
was under the impression that that was necessary to ensure that the
attribute gets forwarded to Tomcat which in this case I don't want it
to be since I'll be using REMOTE_USER instead.

On Wed, Nov 6, 2013 at 8:30 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 11/6/13, 7:34 PM, "Bradley Wagner" <bradley.wagner at hannonhill.com>
> wrote:
>
>>Is it possible to map an attribute, set it as the REMOTE_USER but then
>>*not* pass the attribute along in the forwarded request.
>
> Nate addressed the solution, but for the record, no, you can't do that. If
> it isn't mapped to something, it can't be referenced to end up in
> REMOTE_USER.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net