<div dir="ltr">Ok thanks Paul and Scott. It seems like relay state might be a solution.<div><br></div><div>I changed the relay state setting on my SP and can now see the requested URL passed as parameter to the IDP. The IDP responds with a 302 though to the AuthnEngine servlet, without the relay state parameter. If I can make an educated guess, the IDP must store the relay state somewhere for eventual sending back to the SP. From my custom login handler, where can I get it?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 15, 2014 at 1:08 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">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="">On 8/15/14, 11:26 AM, "Daniel Gay" <<a href="mailto:daniel.gay@quentinsystems.com">daniel.gay@quentinsystems.com</a>> wrote:<br>
><br>
>It's step 5 that I'm unclear as to the best way to do that. The token<br>
>(well really, I'd like the whole URL) gets lost in the redirects, but I<br>
>was hoping that the original URL would be sent to the IDP and that I'd<br>
>somehow have that info available to my custom code.<br>
><br>
>Is this possible? Any thoughts or direction greatly appreciated.<br>
<br>
</div>Anything is possible but access to the URL is prevented by design in the<br>
SAML protocol other than by using RelayState and making assumptions that<br>
only apply if you control both ends.<br>
<br>
The formal way to do what you're after is with a SAML extension in the<br>
AuthnRequest.<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><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Daniel Gay<br></div>Quentin Systems LLC<br>571-249-4783</div>
</div>