Remote IdP not responding?

[Cantor, Scott]

On 7/1/13 8:10 PM, "Roger Jagoda" <rberryj3 at gmail.com> wrote:
>
>What is the best way of forcing the redirection to the appropriate
>URL. In this case that is:
>
>      https://shibboleth.testdb.idp2.edu/idp/profile/SAML2/Redirect/SSO
>
>As you have discussed in the past, we're trying not to use
>ApplicationOverride, and since we're maintaining the Metadata locally,
>we cannot use an entityID:

Where the metadata comes from doesn't make a difference, you specify the
IdP with an entityID.

>Does that leave us with a SessionInitiator?

That already is a SessionInitiator, it's just a shorthand.

>Perhaps something like this:
>
>          <SessionInitiator type="Chaining" Location="/Login"
>id="idptest"
>                relayState="cookie"
>
>entityID="https://https://sso.brown.edu/idp/profile/SAML2/Redirect/SSO">

That's not an entityID, it's an endpoint. You don't specify endpoints
explicitly, that comes from the metadata.

>What does "/Login" refer to? Is it the local directory on the SP or
>the suffix on the IdP URL?

Neither, it's the virtual suffix for invoking a handler inside the
software.

>If the former, should /Login be changed to /secure (see our vhost lines
>above)?

Absolutely not.

-- Scott