Remote IdP not responding?

Cantor, Scott cantor.2 at osu.edu
Fri Jul 5 12:39:14 EDT 2013


On 7/5/13 11:00 AM, "Roger Jagoda" <rberryj3 at gmail.com> wrote:

>We have their IdP SSO lines:
>
><SSO entityID="https://shibboleth.testdb.idp2.edu">
>       SAML2 SAML1
></SSO>

Then you're done. There's nothing else needed, certainly nothing in
Apache, to tell it what IdP to use.

>The latest try (with the native.log error) was with the vhost change
>in the location block:

And I don't understand why you're doing that. You don't need to set the
entityID there if it's already set in the <SSO> element.

>(in using that we commented out the SSO entityID from the IdP point,
>(which is what you picked up on):

Well, don't do that. That's going to break the whole thing.

>In our other SPs, we will have to use the Location Block changes  as
>we have the same service for many IdP sources.
>But that's another thread.

Setting entityID via Apache simply overrides the default value set in the
<SSO> element. That's it.

>We changed the above to another IdP (not supplied by local file but by
>the actual <SSO> URL):
>
>
>            <SSO entityID="https://shibboleth2.shidb.idp2.edu">
>              SAML2 SAML1
>            </SSO>
>
>and everything works just fine.

Then I guess it depends what the actual error is, and then what's in the
metadata.

-- Scott




More information about the users mailing list