Closed Bug 867748 Opened 7 years ago Closed 7 years ago
OAuth2 Error recovery flow from account settings
355 bytes, text/html
No description provided.
We need to parse WWW-Authenticate response header in the status 401 case to determine the cause and if it looks like expiry we notify the main thread (propagate up through CalDAV lib) to show the OAuth2 flow again to force a re-authentication. The UX here is still being decided upon.
blocking-b2g: --- → tef?
Summary: Handle refresh_token expiry in oauth2 cases and allow the user to reauthenticate → OAuth2 Error recovery flow from account settings
Pointer to Github pull-request
Comment on attachment 747774 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/9652 OK- here is the new error handling logic... In addition to your usual through reviews It would be majorly helpful to go through and retry _everything_ related to setting up and editing accounts... To test a normal CalDAV case changing your password is required. For the Google OAuth2 case you must follow these steps: Click your username somewhere Click account Click security (on the left ) Directly under "Connected applications and sites" and on the right click "manage access" revoke "testing oauth"
blocking-b2g: tef? → tef+
Target Milestone: --- → 1.0.1 IOT1 (10may)
For reference, I think the URL of the page to invalidate tokens is: https://accounts.google.com/b/0/IssuedAuthSubTokens
Assignee: nobody → jlal
Whiteboard: [status: needs review]
Attachment #747774 - Flags: review?(gaye) → review+
Attachment #747774 - Flags: review?(kgrandon) → review+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
QA Contact: jsmith
Whiteboard: [status: needs review] → [status: needs review][NO_UPLIFT]
Whiteboard: [status: needs review][NO_UPLIFT] → [status: needs review]
Marking verified to indicate that there has been an informal test pass done on this feature. Note that there's more testing to be done here in a more formal analysis, but I'm marking verified to indicate that this has been looked at.
You need to log in before you can comment on or make changes to this bug.