<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Mike,<div><br></div><div>Yes, I think this is the case. Is there a reason why or a situation in which you could imagine the IdP caring about the users' destination URL that prompts you to wonder?</div><div><br></div><div>Thanks,</div><div>Nate.</div><div><br><div><div>On Sep 3, 2012, at 14:20 , Grady, Michael Allen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Is the same true when passing the parameter "target" to the IdP Unsolicited SSO endpoint? The IdP doesn't care what the value is, considers it an opaque string, and passes it to the SP as RelayState?</span></blockquote></div><br></div></body></html>