GoogleOAUTH: 请求中的重定向 URI 与注册的重定向 URI 不匹配

我正试图从我的 Java 网络应用程序上传到 YouTube，我花了几天的时间来了解问题是什么，在哪里，我不能得到它，因为现在我把我的头发从我的头上。

我注册了我的网络应用在谷歌控制台，所以我得到了一对客户端 ID 和秘密，并有可能下载 JSON 类型的文件与我的配置。

配置如下:

{
"web":{
"auth_uri":"https://accounts.google.com/o/oauth2/auth",
"client_secret":"***",
"token_uri":"https://accounts.google.com/o/oauth2/token",
"client_email":"***",
"redirect_uris":["http://localhost:8080/WEBAPP/youtube-callback.html","http://www.WEBAPP.md/youtube-callback.html"],
"client_x509_cert_url":"***",
"client_id":"***",
"auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs",
"javascript_origins":["http://www.WEBAPP.md/"]
}
}

我怎么可能从谷歌得到默认的网址？

The redirect URI in the request: http://localhost:8080/Callback did not match a registered redirect URI

它总是给我默认的 http://localhost:8080/Callback URL，而不是我的。

IDE 控制台显示:

请在浏览器中打开下列地址: Https://accounts.google.com/o/oauth2/auth?client_id=***&redirect_uri=http://localhost:8080/callback&response_type=code&scope=https://www.googleapis.com/auth/youtube.upload 现在尝试在默认浏览器中打开该地址...

我正在使用依赖项的最后一个版本: Google-api-services-youtube v3-Rev99-1.17.0-rc 和 < em > google-api-services-youtubeAnalytics v1-rev35-1.17.0-rc

168810 次浏览
小开

You need to go into the developer console and set 

http://localhost:8080/WEBAPP/youtube-callback.html

as your callback URL.

This video is slightly outdated, as it shows the older Developer Console instead of the new one, however, the concepts should still apply. You need to find your project in the developer console and register a callback URL.

小开
最佳答案

When your browser redirects the user to Google's oAuth page, are you passing as a parameter the redirect URI you want Google's server to return to with the token response? Setting a redirect URI in the console is not a way of telling Google where to go when a login attempt comes in, but rather it's a way of telling Google what the allowed redirect URIs are (so if someone else writes a web app with your client ID but a different redirect URI it will be disallowed); your web app should, when someone clicks the "login" button, send the browser to:

https://accounts.google.com/o/oauth2/auth?client_id=XXXXX&redirect_uri=http://localhost:8080/WEBAPP/youtube-callback.html&response_type=code&scope=https://www.googleapis.com/auth/youtube.upload

(the callback URI passed as a parameter must be url-encoded, btw).

When Google's server gets authorization from the user, then, it'll redirect the browser to whatever you sent in as the redirect_uri. It'll include in that request the token as a parameter, so your callback page can then validate the token, get an access token, and move on to the other parts of your app.

If you visit:

http://code.google.com/p/google-api-java-client/wiki/OAuth2#Authorization_Code_Flow

You can see better samples of the java client there, demonstrating that you have to override the getRedirectUri method to specify your callback path so the default isn't used.

The redirect URIs are in the client_secrets.json file for multiple reasons ... one big one is so that the oAuth flow can verify that the redirect your app specifies matches what your app allows.

If you visit https://developers.google.com/api-client-library/java/apis/youtube/v3 You can generate a sample application for yourself that's based directly off your app in the console, in which (again) the getRedirectUri method is overwritten to use your specific callbacks.

小开

I think I encountered the same problem as you. I addressed this problem with the following steps：

1) Go to Google Developers Console

2) Set JavaScript origins:

3) Set Redirect URIs:

小开

I was able to get mine working using the following Client Credentials:

Authorized JavaScript origins

http://localhost

Authorized redirect URIs

http://localhost:8090/oauth2callback

Note: I used port 8090 instead of 8080, but that doesn't matter as long as your python script uses the same port as your client_secret.json file.

Reference: Python Quickstart

小开

I thought I had this configured but it turns out I set the URL in the wrong place. I followed the URL provided in the Google error page and added my URL here. Stupid mistake from my part, but easily done. Hope this helps


提交答案