Help- Attribute is null in request header during authorization

Peter Schober peter.schober at univie.ac.at
Thu Oct 4 04:02:16 EDT 2012


* Milan Ashara <milan.ashara at spec-india.com> [2012-10-04 08:36]:
>     IDP Authenticates succesfully. On URL 
> http://sp-url/Shibboleth.sso/Session we are getting request headers like 
> client address, sso protocol , identity providers, authentication context 
> class, authentication context   decl...etc. But we are not getting any user 
> attributes like uid. We want to authorize user based on uid.
[...]
>     Do we need to do any configuration in attribute-map.xml for 
> idp(https://aai-logon.vho-switchaai.ch/idp/shibboleth).?

Yes, uid is not part of the default attribute-map.xml of the SP.
You'll need to add something like this:

  <Attribute name="urn:oid:0.9.2342.19200300.100.1.1" id="uid"/>

Assuming that the SWITCH VHO IdP issues oid-name formats (which you
could conform with aai at switch.ch). But that won't work now. Read on:

* Milan Ashara <milan.ashara at spec-india.com> [2012-10-04 09:09]:
>     We  have found that we are getting "unable to access local file 
> /etc/shibboleth/attribute-map.xml" in shibd_warn.log.

That means you have changed something that you shouldn't have.
The default install comes with correct settings, of course.
Make sure that file exists and that it's world-readable.

>     No there is no attributes in the Shibboleth SP (transaction.log).

Since the SP cannot map them (due to the error above) I would expect
that. So get the SP to access the file, and then see what attributes
show up. (You could also check your shibd.log for sent attributes now
but you won't be able to make any use of them unless the attribute map
is fixed/in place.)
-peter


More information about the users mailing list