Trouble configuring SP3 for multiple idps

[Will Knight]

That seems to do the trick: I just had to modify the path="secure" to be
path="shibboleth" (since that's where my handler lives)

Thanks everybody! Hopefully this is useful to others.

I was able to successfully perfom a login with one of our internal idps.
Testing with a real outside idp they get an error and the transaction log
looks like:
Shibboleth-TRANSACTION.AuthnRequest|||<entityid>||||||urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect||||||

Is there a way to enable the SP to support HTTP-Redirect?

On Thu, Nov 1, 2018 at 12:21 PM Cantor, Scott <cantor.2 at osu.edu> wrote:

> If none of the data is there, you haven't told the SP it's supposed to
> protect the URL at which the data isn't showing up. If it's IIS then you
> need at least an authType="shibboleth" in the relevant RequestMap portion
> for anything to happen.
>
> Please read the documentation on integrating applications and handling
> sessions (passive vs. active).
>
> -- Scott
>
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>


-- 
Will Knight
Web Developer
Quaver Music LLC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20181101/2d943844/attachment.html>