Convert native Shibboleth SP installation to Shibboleth SP using InCommon metadata

[Cantor, Scott]

On 3/16/12 9:21 AM, "Jason Johnson" <jasonj at terradotta.com> wrote:
>I'm used to going to https://somesite/Shibboleth.sso/Metadata in order to
>generate the metadata for each client site for them to install on their
>IdP.
>My confusion was that there is nothing that tells that to get things
>remotely.  Or I was just doing it wrong.

That has nothing to do with configuring your SP. That's your metadata. You
don't use your own metadata. I don't understand the rest of your comment.

> 
>And, yes, I am looking for multiple metadata sources - InCommon and
>others.

Then just configure multiple sources.

>  What I would also like to do is the following:
> 
>1.  Have both site1.somewhere.com <http://site1.somewhere.com> and
>site2.somewhere.com <http://site2.somewhere.com> use a common SP -
>sp.somewhere.com <http://sp.somewhere.com>.

>  So, in each site, they would have a login link that points to
>sp.somewhere.com/secure <http://sp.somewhere.com/secure>.  This should
>bounce the user to the appropriate login for their site.  Do I have that
>logic right?

If you're talking about load balancing or something like that, then you
should read the topics on clustering. If you're talking about something
else, you've lost me.

-- Scott