Cannot renew access

Bug #1262876 reported by Kai Mast
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Online Accounts setup for Ubuntu Touch
Fix Released
High
Alberto Mardegan
ubuntu-system-settings-online-accounts (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Twitter invalidated my access token for some reason. I can grant new access by using the unity-control-center-signon gui but not using the online-accounts-setup.

(I am on the desktop)

Tags: trusty
Revision history for this message
Kai Mast (kai-mast) wrote :

Problem still occurs for me :(

tags: added: trusty
Revision history for this message
Alberto Mardegan (mardy) wrote :

I think that the plan is to raise a snap-decision request whenever the user needs to re-authenticate on an account, I'll talk to the designers to confirm that is the case, and also to get the exact text to be used in the notification.

Changed in ubuntu-system-settings-online-accounts (Ubuntu):
status: New → Confirmed
Changed in ubuntu-system-settings-online-accounts:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Alberto Mardegan (mardy)
Revision history for this message
Alberto Mardegan (mardy) wrote :

Just to complement the bug report with more information which might be useful for designers (and for myself, when I get back to this):

* WHEN
The need for a user interaction might arise at any time, depending on the remote service's policy. It will typically happen when an access token expires, or when an application requests new permissions or changes its key.

*WHAT
The user interaction could potentially be anything which can be embedded in a website, but typically it will be a login form or a page where the user has to confirm that he authorizes the application to get certain permissions on his account; or even a combination of the two. In any case, this is directly coming from the service provider, and we have no control over it (it's something which we embed in a web view element).

* OUR DATA
What we know about this request is:
- the affected account (which we could show the provider name, the user ID, an icon, etc.)
- the requesting application, *if it is part of a click package*; unfortunately, if the requesting process is a system service (or an application installed as a .deb package), establishing the source of the request will be more difficult.

Initially the plan was to use snap decisions for this, and this is probably the easiest short-term solution for the implementation side:
https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit#heading=h.topn0ejru38u
However, this was never designed in detail, and better solutions might be possible.

Revision history for this message
Alberto Mardegan (mardy) wrote :

This was fixed sometimes ago in the summer.

Changed in ubuntu-system-settings-online-accounts (Ubuntu):
status: Confirmed → Fix Released
Changed in ubuntu-system-settings-online-accounts:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.