Convert native Shibboleth SP installation to Shibboleth SP using InCommon metadata

[Cantor, Scott]

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

Your terminology is confusing here, but to start with, the SP doesn't use "SP metadata", only IdP metadata. So if you're saying you want the SP to be provisioning its IdPs from InCommon instead of a local file, I get it.

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

Again, you don't use SP metadata. You specify IdP metadata remotely by using the XML provider with a url or uri attribute instead of a file or path attribute, and the various other trust related filtering you need.

>  I have seen this line mentioned a few times in other posts:

InCommon has documentation that outlines how to provision the SP with their metadata, yes.

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

Both what?

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

That just means you need multiple metadata sources, InCommon and others.

I think you're under the impression that the SP being "in InCommon" has some impact on its configuration as an SP, but it really doesn't.

-- Scott