Google Drive HTTP 403 "Access Not Configured" error with DrEdit

Question

I'm attempting to install the DrEdit sample app for python onto GAE. The app runs, but saving or opening a file results in an HTTP 403 "Access Not Configured Error".

client.json has client_id and client_secret set per the API Access>Client ID for Drive SDK values. I have also attempted to use the values for API Access>Client ID for web applications.

The Google Drive SDK> OAuth Client ID has also been set variously to the Drive SDK and web app Client IDs.

What am I doing wrong?

question from:https://stackoverflow.com/questions/10368678/google-drive-http-403-access-not-configured-error-with-dredit

Answer 1

In the services section of the Google API console there are two services relating to drive development, SDK and API. When you create a new Drive SDK entry, Drive API service is not automatically enabled (which doesn't make sense, I don't see when you'd create a drive enabled application without using the drive API). Switch the Drive API service on for the project and try again.

@lurking_googlers I think a lot of people will fall for this, doesn't it make sense to enable the API when the SDK is enabled?