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

[Bradley Wagner]

>
> Well, if you don't want anything to get through, yes, removing the prefix
> and not using headers will accomplish that.


Got it. Thanks!


On Wed, Nov 6, 2013 at 10:43 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 11/6/13, 10:27 PM, "Bradley Wagner" <bradley.wagner at hannonhill.com>
> wrote:
> >
> >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.
>
> No, anything mapped is exported by definition.
>
> >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.
>
> Well, if you don't want anything to get through, yes, removing the prefix
> and not using headers will accomplish that.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131107/d65d5045/attachment.html