multiplexing IdP configurations
Tom Scavo
trscavo at gmail.com
Fri Mar 27 16:45:22 EDT 2015
On Fri, Mar 27, 2015 at 4:38 PM, Walter Forbes Hoehn (wassa)
<wassa at memphis.edu> wrote:
> If it’s the host part of the URL that needs to vary, the IdP configuration isn’t even involved, no? That’s a matter of OS/webserver setup and appropriate metadata publishing.
AFAIK there is no amount of savvy metadata publishing that will reduce
down time to zero. Am I missing something? (I will be happy if the
answer is yes :)
Tom
>> On Mar 27, 2015, at 3:31 PM, Tom Scavo <trscavo at gmail.com> wrote:
>>
>> On Fri, Mar 27, 2015 at 4:09 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>>> On 3/27/15, 3:59 PM, "Tom Scavo" <trscavo at gmail.com> wrote:
>>>>
>>>> You can only have one inbound HTTP-Redirect endpoint (e.g.) at the
>>>> IdP. If you want to change the location of that endpoint, you
>>>> necessarily break interoperability until your SP partners have updated
>>>> their metadata.
>>>
>>> No, you can have any number.
>>
>> Oh, I may be on the verge of a revelation :-)
>>
>> So I can configure two HTTP-Redirect endpoints in a V2 IdP (different
>> host, same path) and then safely migrate SP partners by introducing
>> the new endpoint in metadata for as long as needed?
>>
>> Tom
>> --
>> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
>
> --
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
More information about the dev
mailing list