> The metadata the SP sent me was missing those namespaces, what is published by
> InCommon is better, but not complete.
You are not reading the XML correctly.
The XML begins with
<EntitiesDescriptor
xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
xmlns:alg="urn:oasis:names:tc:SAML:metadata:algsupport"
xmlns:ds="
http://www.w3.org/2000/09/xmldsig#"
xmlns:idpdisc="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol"
xmlns:init="urn:oasis:names:tc:SAML:profiles:SSO:request-init"
xmlns:mdrpi="urn:oasis:names:tc:SAML:metadata:rpi"
xmlns:mdui="urn:oasis:names:tc:SAML:metadata:ui"
xmlns:shibmd="urn:mace:shibboleth:metadata:1.0"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
ID="INC20160906T191312" Name="urn:mace:incommon"
validUntil="2016-09-20T19:13:12Z">
The default namespace is declared by
xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
So the default namespace is
urn:oasis:names:tc:SAML:2.0:metadata
Thus this element (which today begins on line 250617 of the
InCommon metadata)
<EntityDescriptor entityID="
https://shibbsp.smartcatalogiq.com/shibboleth">
is fully
<urn:oasis:names:tc:SAML:2.0:metadata:EntityDescriptor entityID="
https://shibbsp.smartcatalogiq.com/shibboleth">
> Looking at their metadata directly from InCommon's published metadata, you can
> see not all the namespaces are there
They are indeed there. The InCommon metadata is well formed,
which is important since thousands of clients download, parse,
and consume it each day.
> and plugging it into SimpleSAML generates
> an exception:
You need to understand namespace inheritance as Tom pointed
out. Since the <EntityDescriptor> does not directly have a
namespace declared it is inheriting
urn:oasis:names:tc:SAML:2.0:metadata
If you copy the <EntityDescriptor> but do not add the
inherited namespace like
<EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata" entityID="
https://shibbsp.smartcatalogiq.com/shibboleth">
then yes, you will receive an exception, but it is due to your
error in not handling the namespace inheritance correctly
rather than the InCommon metdata being ill formed.
Scott K