No metadata returned for SP with matching protocol

[Wessel, Keith]

Got it. I suspect I'm not doing a schema validation on our local metadata because fo some old less-than-perfect metadata that I inherited whenI took the service over. Looks like I need to clean that up so I can turn the validation filter on to prevent issues like this in the future.

Keith


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

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

I meant was the invalid EntityDescriptor element embedded in a valid EntitiesDescriptor or was the whole XML document invalid to start with. But what matters isn't what they sent, it's what you loaded.

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

Probably it did, so you stripped the namespace and it got broken at that point, but was embedded into a metadata file with at least something valid in it.

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

I'm not sure it would have if the root element had been invalid, but that's still not good. OTOH, if you want to be rigrous, you slap the schema validation filter in there, and then I know it wouldn't have worked.

-- Scott

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