Attribute not resolving on SP
Stein, Eric
steine at locustec.com
Thu Apr 18 12:53:28 EDT 2013
Peter,
I'm not using mod_proxy or mod_proxy_ajp right now. I don't remember anything anywhere mentioning I needed to configure this. I don't suppose you know what I need to do here, or can point me to relevant documentation?
I did just add uid to REMOTE_USER in shibboleth2.xml.
Thanks,
Eric
-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Peter Schober
Sent: Thursday, April 18, 2013 12:21 PM
To: users at shibboleth.net
Subject: Re: Attribute not resolving on SP
* Christopher Bongaarts <cab at umn.edu> [2013-04-18 18:14]:
> > What specific java call can I make so that my JSPs can see the UID?
>
> https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPAttribute
> Access
>
> Examples at the bottom include Java...
>
> request.getAttribute("Shib-Identity-Provider")
>
> or in your case
>
> request.getAttribute("uid")
If mod_proxy is bein gusead (instead of mod_proxy_ajp) tuning the attributes into HTTP request headers in the Shib SP will be necessary.
Without that (and without using AJP) neither request attributes nor request headers will be visible in Java.
Provided (in this case) "uid" is part of the REMOTE_USER precedence list in shibboleth2.xml the authenticated subject will be seen in httpd's access log (look for lines not containing ' - - '). So I'd check that first.
-peter
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list