Commit 50597887 authored by kochi@chromium.org's avatar kochi@chromium.org

Use auth/drive scope, instead of auth/drive.file scope

For full access to Drive, we need less restrictive scope.
https://www.googleapis.com/auth/drive.file only allows accessing files
which is created on its own (i.e. Chrome), which is useless for
file browser purpose. Instead, we have to use
https://www.googleapis.com/auth/drive scope.

BUG=chromium:127728
TEST=none

Review URL: https://chromiumcodereview.appspot.com/10832201

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150518 0039d316-1c4b-4281-b951-d872f2087c98
parent f2aaf05e
......@@ -50,7 +50,7 @@ const char kUserContentScope[] = "https://docs.googleusercontent.com/";
const char kContactsScope[] = "https://www.google.com/m8/feeds/";
// OAuth scope for Drive API.
const char kDriveScope[] = "https://www.googleapis.com/auth/drive.file";
const char kDriveScope[] = "https://www.googleapis.com/auth/drive";
const char kDriveAppsScope[] = "https://www.googleapis.com/auth/drive.apps";
const char kDriveAppsReadonlyScope[] =
"https://www.googleapis.com/auth/drive.apps.readonly";
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment