SP Metadata Question

[Mr. Christopher Bland]

Hi All,

I recently started working with a vendor who has InCommon metadata.  What’s weird to me is that they have metadata that includes a single entityID, a single cert and ACSs with different domains. 

    <md:AssertionConsumerService xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" index="1" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://hosta.example.com//Shibboleth.sso/SAML2/POST"/>
    <md:AssertionConsumerService xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" index="2" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://hostb.example.com/Shibboleth.sso/SAML2/POST"/>
    <md:AssertionConsumerService xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" index="3" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://completely.different.domain/Shibboleth.sso/SAML2/POST”/>

I was under the impression that if I wanted to have a single SP handle multiple domains I would need to do application overrides for each of the hosts.  Thought this might solve a problem I have where I have built  a multisite subdomain Wordpress server that does domain mapping for individual blogs/sites.  The SPv3 ApplicationOverridedocs section mentions host based vs path based overrides but it’s unclear to me how I create metadata for my IDP to recognize all of the ApplicationOverride URLs.  I am wondering if this is what the vendor is doing.

I appreciate any thoughts,

-Chris