How to set relayState

[Cantor, Scott]

On 7/16/12 5:21 PM, "Rob Whitener" <rob.whitener at audaxhealth.com> wrote:
>
>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?

That means there are two requests happening, one to each URL. If one of
them is the "final" outcome, then it's the second one coming in and the
one that actually is making it to the IdP.

All you have to do is remove the setting and the URLs will be literally
sent, but the outcome will be the same, just easier to see happening.

>  The homeUrl in our Application is set to /partner/bigOrg, so does that
>affect relayState for SP initiated SSO?

The homeURL is relevant only when no state exists or the state is
unrecoverable.

>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.

Usually the SP is the one insisting on URL-per-partner designs because it
avoids the need for discovery.

But this isn't really about relay state, your web server is simply not set
up to allow whatever it is you want to do with URLs.

-- Scott