Embedded Discovery Service and Cookie cacheExpiration

[Dan McLaughlin]

None of our end users use more than one IdP, and there is no need to
correct for mistakes since the DS page will continue to display until
they've successfully authenticated to their agency.  So to continually
show them the DS selection page doesn't make since for us.

I'm not sure I'm following your suggestion.  Is there an example
somewhere I can look at?

--

Thanks,

Dan McLaughlin


On Thu, Oct 20, 2011 at 9:46 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 10/20/11 10:18 PM, "Dan McLaughlin" <dmclaughlin at tech-consortium.com>
> wrote:
>>
>>Once a user has successfully logged into their IdP this configuration
>>would effectively stop the user from ever seeing the Discovery Service
>>selector page for one year, unless they cleared their cookies.
>
> That makes it impossible to use more than one, or correct for mistakes. It
> also creates inconsistency in the user experience.
>
>>There doesn't seem to be anyway to configure the Embedded Discovery
>>Service to have the same behavior, or am I missing something?
>
> I don't believe it supports that for the reasons above. You could probably
> achieve the same outcome by combining the EDS with the SP's "Cookie"
> SessionInitiator, which can be configured to automatically follow the SP
> history cookie, which is the same cookie format used by the EDS.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>