Timeline for Logging out so another user can log in
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2012 at 7:43 | comment | added | jogloran |
Specifically, the value of se-usr seems to be responsible. But never allowing it to be set breaks the authentication flow.
|
|
| Aug 21, 2012 at 5:49 | comment | added | jogloran |
After some experimentation, I don't think Local Storage is the culprit. Before and after authentication via Google, localStorage is empty, and I've verified that localStorage.clear() does work in UIWebView. So my suspicion is that one of the cookies is responsible for caching the user's logged-in status.
|
|
| Aug 20, 2012 at 23:57 | comment | added | jogloran | Thanks, Kevin. Unfortunately iOS support for managing Local Storage is fairly poor, and very poorly documented. Is there any other mechanism at all for doing this? While messing about with cookies, I noticed that if I immediately delete any cookies as they're added in the authentication flow, I get the "select provider" screen, but as expected, authentication won't proceed properly because cookies can't be saved. Is there a particular cookie name which I can purge? | |
| Aug 20, 2012 at 17:25 | history | answered | Kevin Montrose | CC BY-SA 3.0 |