Help- Attribute is null in request header during authorization

[Milan Ashara]

Hello kevin.foote,

    Thank you for your suggestion.

    We are using IDP https://aai-logon.vho-switchaai.ch/idp/shibboleth. We 
are configuring SP that uses idp as 
https://aai-logon.vho-switchaai.ch/idp/shibboleth.

    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.

    There is no attribute-filter.xml  in SP, it might be in IDP.

    Do we need to do any configuration in attribute-map.xml for 
idp(https://aai-logon.vho-switchaai.ch/idp/shibboleth).?

Thanks
Milan Ashara



> Have you released the particular attribute to the SP in question at the
> IdP? This is done in the attribute-filter.xml file?
>
> Does your SP in question have the correct mapping of that attribute in
> the attribute-map.xml file?
>
> Is your particular attribute listed at the SP-url /Shibboleth.sso/Session 
> after
> authentication and authorization happen?
>
> List members need more information to give you any sort of help.
>
> ------
> thanks
>  kevin.foote
>
> On Wed, 3 Oct 2012, Milan Ashara wrote:
>
> -> Hello,
> ->
> -> After IDP Authenticate user, it redirects to URL. where I have used 
> filter in java to authorize user. I am not getting any attribute header / 
> cookie (UID is null)  from which I authorize user.
> ->
> -> Any suggestion where is the problem?.
> ->
> -> Thanks in advance
> ->
> -> Milan D Ashara
> ------------------------------