<div dir="ltr"><div>Scott,</div>
<div>Thanks for the fast and the detailed answer!</div>
<div>Michael<br><br></div>
<div class="gmail_quote">On Tue, Aug 16, 2011 at 3:41 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On 8/15/11 11:21 PM, "Michael Furman" <<a href="mailto:furman.michael@gmail.com">furman.michael@gmail.com</a>> wrote:<br>>1) According to my understanding the SAML protocol does not define how<br>
>the information from the assertion is added to a browser.<br><br></div>That's correct.<br>
<div class="im"><br>>So, please clarify me if Set-Cookie is part of SAML2 protocol or it is<br>>addition of Shibboleth to set the state of SAML2 authentication in a<br>>browser.<br><br></div>Session handling is outside the scope of the standard.<br>
<div class="im"><br>><br>>2) What happens if my application accesses other DNS domain?<br><br></div>The SP at that domain repeats the process.<br>
<div class="im"><br>>According to my knowledge a browser will not send a cookie.<br>>How Shibboleth solves this problem?<br><br></div>It doesn't. Web SSO is the act of creating a session with one domain based<br>
on a session with another.<br><br>-- Scott<br><font color="#888888"><br>--<br>To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br></font></blockquote>
</div><br></div>