Remote IdP not responding?

[Cantor, Scott]

On 6/27/13 7:13 PM, "Roger Jagoda" <rberryj3 at gmail.com> wrote:
>However, when we try a protected page from our SP server, we see these
>errors:
>
>shibd.log:

Yes, but that has nothing to do with the metadata error itself, what does
the relevant part of the log say?

>>
>         backingFilePath="/tmp/shibboleth/testdb.idp2-metadat.xml"

It's a fairly bad idea to use /tmp for that. Or anything else really that
needs to last more than 5 minutes. Let the system generate the path, don't
specify one.

>Just in case, we added the local MetaFile that we were able to
>download from any browser:
>
>        <MetadataProvider type="XML"
>file="/tmp/shibboleth/testdb.idp2-metadat.xm"/>

Do NOT do that, you don't want duplicate metadata. If the file were even
there, it would work, so I suppose it's not. Or it's incorrect metadata at
the source and isn't valid, or maybe even with something loaded, the
entityID in use isn't what's in the metadata.

>The REALLY stange thing is that we can use CURL and still access the
>remote meta from the SP Server itself:

If I were taking a wild guess, it would be that you're on Red Hat 6 and
don't have the custom libcurl in place and in use, but that's guessing.
The log will tell you what the problem is.

-- Scott