No metadata returned for SP with matching protocol

[Wessel, Keith]

Sorry, was what embedded in the metadata? The xmlns attribute for each and every element? No, not a single mention of xmlns.

The vendor sent me their metadata wrapped in EntitiesDescriptor tags. It was a single EntityDescriptor, though, plus I was adding it to our local metadata file that was already wrapped in EntitiesDescriptor tags. So, I removed the EntitiesDescriptor tags from the outside of the vendor metadata before adding itto ours. I'm not sure, if this point, if their EntitiesDescriptor opening element had an xmlns attribute.

I've advised the vendor to distribute their metadata without the EntitiesDescriptor elemenets in the future.

But yes, I was surprised it loaded without an error.

Keith


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

> 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.

Maybe Brent knows differently, but that doesn't seem like it should load "successfully". Was it embedded in other metadata?

I do think we should have the DEBUG option to just log outright every entityID it loads. The SP does that, I think.

-- Scott

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