My favorites | Sign in
Project Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 12: Flows should be ended more agressively when authentication tokens go away or are replaced
1 person starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  mike.wak...@gmail.com


Sign in to add a comment
 
Reported by mike.wak...@gmail.com, Oct 26, 2009
For certain authentication methods, there is a strong signal that the user
is done pouring. Example: onewire token is removed. In this case, the core
should be able to end the flow sooner than the idle timeout.

If another authentication token has appeared, this should be an even
stronger signal that the flow should be ended (and replaced with that of
the new user.)
Sign in to add a comment

Hosted by Google Code