AuthenticationContext persistence

[Klingenstein, Nate]

So active in this sense is... active only on this... what?  I would have assumed that a view state was terminal for a particular request since it has to be viewed by a user.  Clearly, I need to start again from scratch and really understand where message dispatch can happen.

This onion has many layers. Many non-linear layers.

Sorry for the trouble.

Semt frim mt iPone

> On Aug 29, 2016, at 17:28, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
>> On 8/29/16, 8:21 PM, "dev on behalf of Klingenstein, Nate" <dev-bounces at shibboleth.net on behalf of nklingenstein at calstate.edu> wrote:
>> 
>>   The authentication context appears to persist across requests(e.g. getActiveResults)
> 
> It does not. The context tree is always unique to every request. If anything in it has to be saved across requests, that has to be loaded and saved by the flows. None of the context objects themselves are ever persistent.
> 
> -- Scott
> 
> 
> 
> -- 
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net