Google API身份验证:客户端的来源无效 [英] Google API authentication: Not valid origin for the client

查看:479
本文介绍了Google API身份验证:客户端的来源无效的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在向Google API(gapi)发出验证请求时,它将在checkOrigin上返回false。



我已经删除了任何将直接链接的客户端ID或任何内容到我的帐户,并用一个正则表达式替换它,表明数据是供参考的。



网址: https://accounts.google.com/ o / oauth2 / iframerpc?action = checkOrigin& origin = https%3A%2F%2Flocal.tools& client_id =(\d {21})

我的原始网址是本地网址,它是 https://local.tools



结果: {valid:false}



我使用这里找到的示例没有偏差(除了用clientid替换我的21位数字密码): https:// ga-dev- tools.appspot.com/embed-api/third-party-visualizations/



我试图展示的项目在演示网站上很好地显示,但没有越过t他在我的local.tools站点上的客户端错误无效。

解决方案

此示例: https://developers.google.com/analytics/ devguides / reporting / embed / v1 / getting-started



文档说不要忽视两个关键步骤(当您阅读说明时,您不会忽视这两个关键步骤:
启用Analytics API [&]设置正确的来源),但没有明确说明要设置正确来源的地点。



由于我的客户端ID不起作用,我创建了一个新项目和一个新的客户端ID。新项目可能没有必要,但我保留(并使用)它。



以下是有效的工作:





在创建凭证期间,您将看到一个名为限制
输入JavaScript起源,重定向URI或两者的部分。这是您可以输入您的来源的地方。



保存并复制您的客户ID(和秘密)。

我的脚本在创建新的OAUTH凭证后分配了原点,并在此过程之后使用了新生成的客户端ID。

When making an auth request to the Google API (gapi), it's returning false on the checkOrigin.

I have removed any client id's or anything that would link directly to my account and replaced it with a regex indicating what the data is for reference.

Url: https://accounts.google.com/o/oauth2/iframerpc?action=checkOrigin&origin=https%3A%2F%2Flocal.tools&client_id=(\d{21})

My origin url is a local url, which is https://local.tools

Result: {valid: false}

I'm using the example found here without deviation (except for replacing clientid with my 21 digit clientid): https://ga-dev-tools.appspot.com/embed-api/third-party-visualizations/

The items I'm trying to display show up nicely on the demo site, but aren't getting past the Not valid origin for the client error on my local.tools site.

解决方案

I received the same console error message when working with this example: https://developers.google.com/analytics/devguides/reporting/embed/v1/getting-started

The documentation says not to overlook two critical steps ("As you go through the instructions, it's important that you not overlook these two critical steps: Enable the Analytics API [&] Set the correct origins"), but does not clearly state WHERE to set the correct origins.

Since the client ID I had was not working, I created a new project and a new client ID. The new project may not have been necessary, but I'm retaining (and using) it.

Here's what worked:

During creation of the credentials, you will see a section called "Restrictions Enter JavaScript origins, redirect URIs, or both". This is where you can enter your origins.

Save and copy your client ID (and secret).

My script worked after I created the new OAUTH credential, assigned the origin, and used the newly generated client ID following this process.

这篇关于Google API身份验证:客户端的来源无效的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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