diff options
| author | sail@chromium.org <sail@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-09-06 18:30:49 +0000 |
|---|---|---|
| committer | sail@chromium.org <sail@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-09-06 18:30:49 +0000 |
| commit | ae3b19fcd7fc940f8141408c7ee5cf913ec35004 (patch) | |
| tree | 7b866bc23f9909758fae45f084c9b2df14762209 /native_client_sdk/src | |
| parent | f46422ca224d85dea37d054b1f4c362b77bb9e66 (diff) | |
| download | chromium_src-ae3b19fcd7fc940f8141408c7ee5cf913ec35004.zip chromium_src-ae3b19fcd7fc940f8141408c7ee5cf913ec35004.tar.gz chromium_src-ae3b19fcd7fc940f8141408c7ee5cf913ec35004.tar.bz2 | |
Revert 221035 "Revert 219146 "[sync] Force re-auth during sync s..."
Restoring the change. Verified that this was not the cause of bug 278543.
> Revert 219146 "[sync] Force re-auth during sync setup if Oauth2 ..."
>
> > [sync] Force re-auth during sync setup if Oauth2 token is unavailable
> >
> > If an enterprise user disables sync via a dashboard clear, and goes on
> > to re-enable sync at a later time, set up can fail due to an expired or
> > missing Oauth2 token.
> >
> > This patch updates SyncSetupHandler::OpenSyncSetup to first check if an
> > auth token is available for sync, and if not, force a re-auth.
> >
> > R=atwilson
> > TBR=fgorski,rogerta
> > BUG=276650
> > TEST=Disable sync for an enterprise user, exit chrome, delete "Web
> > Data*" from the profile dir, restart chrome, and set up sync. Re-auth
> > must be forced in this case.
> >
> > Review URL: https://chromiumcodereview.appspot.com/23005016
>
> TBR=rsimha@chromium.org
>
> Review URL: https://codereview.chromium.org/23759003
TBR=sail@chromium.org
Review URL: https://codereview.chromium.org/23458028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221740 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'native_client_sdk/src')
0 files changed, 0 insertions, 0 deletions