metadata UI displayname and multiple application overrides

[Chad La Joie]

I don't know about InCommon but I've certainly worked with a number of
customers who provide "Shibboleth SP services to multiple customer
sites within a single SP".

The real question is what you're trying to accomplish.  If you're
trying to make it look like one service, then you make it look like
one  service.  One name, one UI, one entity ID, etc.  If you're trying
to make it appear as if you're running a unique service for every
customer then set it up that way.  N names, N UIs, N entity IDs, etc.
You'll only run in to trouble if you try and do some half-way
solution.

On Mon, Apr 16, 2012 at 14:27, Jeff Silverman <jeff at moodlerooms.com> wrote:
> Hi, all. A cursory examination of the InCommon Metadata tells me that we are
> among only a very few doing this[1] the way we are doing it. I'm not sure
> why that is, but it is probably a combination of reasons which may not be
> relevant here.
>
> For now, thanks for the help on this topic. I'm going to emulate what I'm
> seeing others do, and I'll adjust that if it makes sense in the future.
>
> Thanks,
> Jeff Silverman
>
>
> ([1] where "this" is "providing Shibboleth SP services to multiple customer
> sites within a single SP")
>
> --
> Jeffrey D. Silverman • Moodlerooms, Inc.
> (410) 779-3425 • jeff at moodlerooms.com
> [RE]THINK YOUR LMS
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered