Google Drive HTTP 403“访问未配置” DrEdit错误 [英] Google Drive HTTP 403 "Access Not Configured" error with DrEdit

查看:168
本文介绍了Google Drive HTTP 403“访问未配置” DrEdit错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图将安装DrEdit示例应用程序的python加载到GAE上。该应用程序将运行,但保存或打开文件会导致 HTTP 403访问未配置错误



client.json 根据 API访问> Drive SDK值的客户端ID 设置 client_id client_secret 。我还试图使用 API访问> Web应用程序的客户端ID 的值。 Google云端硬盘SDK> OAuth客户端ID 也已针对云端硬盘SDK和网络应用客户端ID进行了各种设置。

b
$ b

我在做什么错误?

解决方案

在Google API控制台的服务部分有两个与驱动器开发,SDK和API有关的服务。当您创建新的Drive SDK条目时,Drive API服务不会自动启用(这没有意义,我没有看到您何时创建启用驱动器的应用程序而不使用驱动器API)。为项目切换Drive API服务,然后重试。



@lurking_googlers我认为很多人会为此付出代价,启用SDK启用时的API?


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?

解决方案

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?

这篇关于Google Drive HTTP 403“访问未配置” DrEdit错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆