You are right, just was not sure if this was a general SAML or implementation specific question (since I am using Shibboleth Idp).<div><br></div><div>Thanks<br><br><div class="gmail_quote">On Fri, Jan 20, 2012 at 11:18 AM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 1/20/12 2:01 PM, "Anand Somani" <<a href="mailto:meatforums@gmail.com">meatforums@gmail.com</a>> wrote:<br>
<br>
>But the problem is how to get the original application URL that triggered<br>
>the SP to do SSO. So one thought was to pass it as a query param to IDP<br>
>along with SAMLRequest and then hopefully get it back from IDP and then<br>
>use that to finally forward the user once it has been authorized. This<br>
>gives the SP an ability to be stateless and not having to remember where<br>
>the original URL.<br>
<br>
</div>This is addressed in the relevant SAML bindings using RelayState. You<br>
should read the SAML standard if you're trying to implement something, and<br>
you wouldn't need to ask the question if you weren't. It's also not a<br>
Shibboleth question; there is a saml-dev list at OASIS for implementers to<br>
use.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Scott<br>
<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></span></blockquote></div><br></div>