How to set relayState

[Rob Whitener]

I noticed, when looking at the HTTP traffic, that there are actually two
shibstate entries in the cookies, one for /partner/bigOrg and one for
/partner/bigOrg/littleOrg.  I will look more into the webserver config to
see what is going on, but do both of those entries make up the relayState?
 The homeUrl in our Application is set to /partner/bigOrg, so does that
affect relayState for SP initiated SSO?

I am trying to make sure I am working with relayState the right way because
I don't want our partner to force us off spec because they want to get out
of a little dev work.

On Mon, Jul 16, 2012 at 5:05 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 7/16/12 5:02 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
> >
> >>What I have noticed is the browser is redirected to /partner/bigOrg,
> >>which isn't really what I wanted, but there is a cookie named
> >>_shibstate_**** that has the URL I want in it.
> >
> >That isn't possible. Using "cookie" for relayState will result in the URL
> >being stored off in the shibstate cookie, and then that's where it will
> >redirect you after the POST. You can easily verify that with a browser
> >plugin like LiveHeaders.
>
> The correlary to this is that if you're ending up at /partner/bigOrg, then
> your web server caused the SP's redirect to /partner/bigOrg/littleOrg to
> be rewritten or secondarily redirected to /partner/bigOrg. All of that is
> out of the SP's hands.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20120716/ab12fd93/attachment.html