No metadata returned for SP with matching protocol

[Wessel, Keith]

Thanks, all. Problem resolved. The EntityDescriptor element was missing an xmlns attribute. The metadata was still loading, but we ended up getting the error that there was no protocol in metadata matching the one requested.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, January 13, 2016 10:14 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: No metadata returned for SP with matching protocol

On 1/13/16, 10:40 AM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:



>I've turned up logging to debug for org.opensaml.saml but only see messages that my metadata file was successfully processed and loaded. It's not logging any individual entity descriptor IDs, but I can only assume this means I have a sound XML document and that the metadata, or at least its structure or syntax, isn't my problem. Are there any other classes that I might turn up logging for to further verify this, or is my assumption correct?

If the resolver classes are being logged, that's it I think.

>And if my assumption is correct, any other thoughts on why I might be getting the error and log messages that started this thread?

Generally it means somebody's just wrong on something. There's a bogus character somewhere or the metadata's not actually what you think it is. You should sanity check things and break the metadata file to make it invalid and make sure that fails to load, etc.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net