Applications that autorefresh

[Paul Hethmon]

To deal with this issue, I key on the login context in my custom login
handler and when I find it missing I direct the user to a page that either
gives them a choice of where to go or the "default" application
automatically. In most of my use cases, that ends up being the right
choice the user wants anyway.

paul

On 7/16/12 6:21 PM, "Chad La Joie" <lajoie at itumi.biz> wrote:

>On Mon, Jul 16, 2012 at 6:16 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>>>That said, my main concern would be dealing with how state/processing
>>>changed in the various cases.  It seems like a whole lot of trouble to
>>>deal with something the SP needs to address anyways.
>>
>> The issue is whether the IdP is stateful on the server side while
>>handling
>> logins. The SP can't do anything about that part. Once it's issued a
>> request, it's out of the loop.
>
>The original question is really an SP issue, not an IdP issue is what
>I meant.   But no, I have no intention of trying to tackle this in
>IdPv3.  The more I think about it the more ways I see for it to
>introduce behavior that would be incredibly difficult to explain or
>diagnose.  So yes, the IdP will gather up state and hold on to it for
>a while when processing a request but it won't hold it for days.
>
>-- 
>Chad La Joie
>www.itumi.biz
>trusted identities, delivered
>--
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net