This bug was fixed in the package account-plugins -
0.10bzr13.02.27-0ubuntu1
---------------
account-plugins (0.10bzr13.02.27-0ubuntu1) raring; urgency=low
[ Ken VanDine ]
* New upstream snapshot
- account-console: fixed a bug where it was failing to store the
credentialsId because it was using the wrong type.
- Use the web-authentication as described in
https://developers.google.com/accounts/docs/OAuth2 (LP: #1029289)
* debian/rules
- Include Google Client Secret.
-- Ken VanDine <[email protected]> Wed, 27 Feb 2013 10:57:27 -0500
** Changed in: account-plugins (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1029289
Title:
Need to authorize my google account each time I boot the computer
Status in Online Accounts: Account plugins:
In Progress
Status in Online Accounts: OAuth2 plug-in:
Unknown
Status in Online Accounts: Sign-on UI:
Fix Released
Status in “account-plugins” package in Ubuntu:
Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
Fix Released
Status in “account-plugins” source package in Quantal:
Fix Committed
Status in “signon-plugin-oauth2” source package in Quantal:
Fix Committed
Bug description:
[Test Case] Sometimes after one day, sometimes after one week, the
system indicator will turn red and the Google account will be marked
as needing reauthentication. Time can vary, but any period shorter
than one month is a symptom of the bug.
[Regression Potential] Minimal: the change to the Google plugin (in
account-plugins) simply changes the authentication method, in a way
that is well-documented. The change in signon-plugin-oauth2 affects
only those accounts/providers which use the OAuth refresh tokens --
which is only Google, at the moment -- and in a way that can't
possibly break any existing functionality; if the new code had some
mistake, the refresh token would be unusable and the system would
automatically fall back to requesting a new access token (which is
exactly what happens now, with this bug).
I'll try to find why the account-plugins package was not uploaded;
indeed, both are required in order to fix this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
