Convert native Shibboleth SP installation to Shibboleth SP using InCommon metadata

[Jason Johnson]

Hello,

I am wanting to convert my existing Shibboleth SP installation from a native (using local SP metadata file AND connecting to IDPs using local metadata files) to an InCommon/Shibboleth SP installation (with my SP metadata being pulled from InCommon).  My biggest hurdle is I don't see where in the shibboleth2.xml file I need to specify that my SP metadata is to now be supplied remotely.  I have seen this line mentioned a few times in other posts:

<MetadataProvider type="XML" uri="https://wayf.incommonfederation.org/InCommon/InCommon-metadata.xml" backingFilePath="incommon-metadata.xml" reloadInterval="7200">
<MetadataFilter type="RequireValidUntil" maxValidityInterval="2419200" />
<MetadataFilter type="Signature" certificate="incommon.pem" />
</MetadataProvider>

However, I was under the impression that this XML attribute was to tell Shibboleth how to interact with the IDPs.  Do I have that wrong?  Does it control both??

My end goal is the following:

1.  Use my new InCommon SP metadata for all my connections
2.  Use InCommon IDPs for those that are in InCommon
3.  Use local IDP metadata files for those not in InCommon
4.  All this using one Shibboleth installation.

Thanks,
Jason