Cross-Context External Authn w/ IdP Initiated SSO

[snekse]

Hmm, that's what I get for poor copy/paste skills....

My _actual_ message in my logs was:
No profile handler configured for request at path: /Unsolicited/SSO

It was missing the SAML2 in the path.

So my next question should hopefully be quick and easy.

When it's indicated for /profile/SAML2/Unsolicited/SSO that it needs
parameters like providerId, do those params have to be query params or form
submitted, or is there flexibility and Shibboleth will be smart enough to
extract them?


On Fri, Jul 25, 2014 at 1:00 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 7/25/14, 1:50 PM, "snekse" <snekse at gmail.com> wrote:
>
> >Related to the  IdP-initiated SSO, should I be able to see the
> >'/idp/profile/SAML2/Unsolicited/SSO'
> > path in my metadata at /idp/profile/Metadata/SAML?
>
> Nope.
>
> >Wondering because I'm running into the error
> >No profile handler configured for request at path: /SAML2/Unsolicited/SSO
>
> That would normally indicate an older configuration without support for it.
>
> >This is in my handler.xml:
>
> Then I have no idea. That's all you need.
>
> -- 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/20140725/e5e1b264/attachment.html