Tomboy Ubuntu One sync plugin should not cache SSO OAuth tokens

Bug #757841 reported by Roman Yepishev on 2011-04-11
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tomboy (Ubuntu)
Ubuntu One Client Engineering team

Bug Description

Binary package hint: tomboy

At the moment, Ubuntu patch for Tomboy stores the credentials retrieved from SSO in its gconf storage. So when the user invalidates the tokens on the web ui or control panel Tomboy won't notice that and will keep trying to use the tokens that are no longer valid receiving 400 BAD REQUEST (or 401 UNAUTHORIZED). The users will not have any other user-friendly solutions except of resetting the sync state which in turn will cause the conflicts to be created.


ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: tomboy 1.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Apr 11 21:06:23 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: tomboy
UpgradeStatus: Upgraded to natty on 2010-12-05 (127 days ago)

Roman Yepishev (rye) wrote :
Changed in tomboy (Ubuntu):
assignee: nobody → Rodrigo Moya (rodrigo-moya)
Changed in tomboy (Ubuntu):
assignee: Rodrigo Moya (rodrigo-moya) → Ubuntu One Desktop+ team (ubuntuone-desktop+)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tomboy (Ubuntu):
status: New → Confirmed
PeterPall (peterpall) wrote :

At least tomboy should try to get new oauth tokens if it sees that the ones it is caching are invalid.
+1 from me.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers