请求https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest时返回HttpError 403,“呼叫者没有权限"; [英] HttpError 403 when requesting https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest returned "The caller does not have permission"

查看:2049
本文介绍了请求https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest时返回HttpError 403,“呼叫者没有权限";的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我使用Gmail API进行生产中的自动电子邮件处理已经有好几个月了.自2020年7月2日以来,突然看到尝试访问Gmail API的错误消息.

I have been using Gmail API to automatic email processing in production for many months now. All of a sudden since July 2, 2020 seeing the error message trying to access Gmail API.

请求 https://www.googleapis.com时,出现

HttpError 403 /discovery/v1/apis/gmail/v1/rest 返回 呼叫者没有权限"

HttpError 403 when requesting https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest returned "The caller does not have permission"

已检查Gmail仪表板,并且凭据处于活动状态,注意到已删除或修改.

Checked Gmail Dashboard and the credentials are active noting was removed or modified.

检查代码,可以确认3-4个月内没有任何更改.

Checked code and can confirm nothing changed for 3-4 months.

而且我们没有使用旧令牌.我们的代码将处理过期的凭证,并进行令牌刷新.

And we are not using old token. Our code takes care of expired credentials and does a token refresh.

还尝试删除token.pickle文件,当使用Gmail身份验证屏幕重新运行重新验证并重新创建token.pickle文件时,但错误消息无法解决.

Also tried removing the token.pickle file, when rerun re-authenticated using the Gmail Auth screen and token.pickle file is recreated however the error message cannot be resolved.

看来Google的情况有所改变.

It looks like something changed in Google's end.

有人可以确认吗?

最近,当进行搜索时,很多ppl都在各种API中看到了这一点,但没有提供可行的解决方案.

When doing a search seems lot of ppl are seeing this in various APIs recently but no viable solution is provided.

推荐答案

这是Google方面的系统级问题:

This is a system-wide issue on Google's side: https://issuetracker.google.com/issues/160441983

这篇关于请求https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest时返回HttpError 403,“呼叫者没有权限";的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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