SessionInitiator for a specific IdP endpoint

[Tom Scavo]

On Thu, Jan 8, 2015 at 4:18 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> Okay, for the archive, I conclude that multiple DiscoveryResponse
>> endpoints are needed at the SP, something like this:
>
> If you don't disable the DS check, yeah, any dedicated initiator would be another DiscoveryResponse to list. Just disabling the check might be simpler

I don't see how that matters. I'm bypassing the DS and requesting the
DiscoveryResponse endpoint directly.

> especially for a test, unless this is using the InCommon DS or something.

No, there is no DS involved. I'm provoking SP-initiated SSO as follows:

https://app.example.org/Shibboleth.sso/Login?entityID=<entityID>

What I want to do is something like this:

https://app.example.org/Shibboleth.sso/Login?entityID=<entityID>&outgoingBinding=<Binding>

If I were to file an issue in the tracker, would you be willing to
take a look at it at some point?

Thanks,

Tom