<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Milan,<div><br><div><div><blockquote type="cite"><div style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px" id="MailContainerBody" leftmargin="0" topmargin="0" canvastabstop="true" name="Compose message area"><div><font face="Calibri">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.</font></div></div></blockquote><div><br></div><div>I'm not sure what filter you're talking about or which SAML service provider your filter is using.</div><div><br></div><div>The IdP is only responsible for sending you an assertion. You can check to see whether the attribute names and values that you expect are in the assertion. Whatever consumes that assertion will be responsible for setting the attributes.</div><div><br></div><div>If you are using the Shibboleth SP, the assertion will be logged in shibd.log on DEBUG. It will also clearly indicate if it received attributes and discarded them. I would, in this order, ensure that the assertion contains the attributes with the right names attribute-map.xml has entries uncommented, checking /Shibboleth.sso/Session after logging in, ensuring that the variables are getting into the Java servlet container, and then making sure that you've written your Java code correctly.</div><div><br></div><div>If you're not using the Shibboleth SP, please consult the service provider that you are using.</div><div><br></div><div>Thanks,</div><div>Nate.</div></div><br></div></div></body></html>