Attribute not resolving on SP

[Cantor, Scott]

On 4/18/13 12:08 PM, "Stein, Eric" <steine at locustec.com> wrote:

>Thanks for answering, Scott. If the SP has the attribute UID, how does my
>application get access to that attribute? httpRequest.getHeaderNames()
>also doesn't have a header named 'uid'. What specific java call can I
>make so that my JSPs can see the UID?

There are a ton of variables involved here.

I believe that even if you have things configured correctly that Java will
provide no accurate list of attribute names or header names, but I can't
be sure. Leaving that aside, the way you access an attribute or a header
is by specifying the name, not using the collections.

But you first have to get it configured.

If you want to use Shibboleth and a Java container, you must front-end
Apache. That means mod_proxy_ajp or mod_proxy_http in most cases. If you
did neither, you have nothing working at all. You have to access the
container through Apache. If you don't know how, you need to read that
documentation for your chosen container and get that working without
Shibboleth.

Having done that, by default the SP provides environment variables, not
headers. Environment variables will not show up in the Java container
without some effort and would only work with Jetty or Tomcat via
mod_proxy_ajp or an older mod_jk connector.

Headers generally will show up more automatically. Headers can be enabled
on the Apache side with ShibUseHeaders On for the relevent content.

A lot depends on what is being used and how.

-- Scott