getPrincipals() typing
Cantor, Scott
cantor.2 at osu.edu
Thu Sep 1 10:06:20 EDT 2016
On 8/31/16, 10:49 PM, "dev on behalf of Klingenstein, Nate" <dev-bounces at shibboleth.net on behalf of nklingenstein at calstate.edu> wrote:
> By definition, I guess, now that I think about it. If you've built a system that is
> so stateless that it is purely client-side, then there's no way the back button could
> matter, even in theory, so long as the client faithfully replays the entire
> request and you haven't drifted out of some time window.
The system is not stateless, webflow state is not client-side at all, and the issue I was talking about is just that if the URL doesn't change, the back button isn't going to cause a flow to run simply because it happens to match the URL.
In contrast to V2: there was a redirect in the middle to /Authn/Whatever. So going back would pass back over /Authn/Whatever and cause that to run, and require special error handling to deal with.
Here, in the general case, all you ever get is a flow restoration exception that fails in one specific way.
-- Scott
More information about the dev
mailing list