Help configuring custom relying party for a relaystate url

[Karla Borecky]

Hi everyone,

I'm sorry if I am asking a stupid question, but I've looked and looked and
I'm at my wit's end.

I am working with a vendor who has just given me these two urls: one is the
"service" url, the other is the "consume" url - and said that previously,
that's all they gave people and it would work. No metadata, so I believe I
am correct in thinking I need to create a custom relying party section for
them.

But using the SAML2SSOProfile doesn't seem to work. When I go to their test
site, it just brings up our IdP's metadata. I assume that's because it
doesn't know what to do with the rest of the URL, maybe? The resulting url
looks like this:

https://idp.smith.edu/idp/shibboleth?RelayState=https%3A%2F%2Ftesting3%2Ehiretouch%2Ecom%2Fadmin%2F%2Fsaml%2Fconsume%2F&SAMLRequest=[snip]

I've tried to figure out how to configure the relying party to work with a
relaystate url, if that is what I should be doing, but the only references
I could find had an RPID in their relaystate string - which they don't have.

If there's no relying party ID in the relaystate url, do they have to fall
under the 'anonymous' relying party section?

If I can/should be using a custom relying party, should I be using a
different profile from SAML2SSO to handle these sort of requests?

Thank you for any help -

color me clueless,

Karla B
-- 
Karla Borecky
Systems Administrator
ITS
Smith College
Northampton, MA 01063
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130820/a85c1779/attachment.html