<div dir="ltr">Ok, thanks for the info. Sounds like my best bet is to re-think the feature.<div><br></div><div>Dan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 15, 2014 at 3:27 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 Aug 15, 2014, at 3:04 PM, Daniel Gay <<a href="mailto:daniel.gay@quentinsystems.com">daniel.gay@quentinsystems.com</a>><br>
wrote:<br>
><br>
>I changed the relay state setting on my SP and can now see the requested<br>
>URL passed as parameter to the IDP. The IDP responds with a 302 though<br>
>to the AuthnEngine servlet, without the relay state parameter. If I can<br>
>make an educated guess, the IDP must store the relay state somewhere for<br>
>eventual sending back to the SP. From my custom login handler, where can<br>
>I get it?<br>
<br>
</div>I don't know that you can. You're not meant to, so it's not really a goal.<br>
<div class="HOEnZb"><div class="h5"><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>
</div></div></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>