Comment 3 for bug 1248326
Revision history for this message
| Mike McCracken (mikemc) wrote Re: Handle invalidated token in a more user-friendly way | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
@Alberto, ubuntuone-
This was the fastest path to code we could be confident in - it reuses most of the previously working code that used the keyring.
Remember, we have custom QML UI for the login screen, which means we have these options:
1. a U1 signon plugin has to display that UI (no plugin exists, and AFAIK, it is not currently supported for plugins to show QML UI on Touch)
2. we add support to libubuntuoneauth for the client app to show the login UI (possible, but not trivial, and breaks the 'everything in online-accounts' goal)
3. in the client, we simply delete the current U1 account via existing tested API in libubuntuoneauth, and show the user a message to go recreate it. This is the fastest way to a better experience - it's a small change, it's well tested and it's only a bit more annoying.
It also doesn't lose any per-app access settings (which would be one reason to avoid just nuking an existing account), because u1 doesn't use any.