missing redirect uri in request
missing the required redirect URI #22
Comments
omerkhanjadoon commented Aug 23, 2018 •
i am getting the following error when i try to run quick.php (which is named as quickstart in google drive api docs) i have copy paste the exact code but getting the error when i run it from my command line
The text was updated successfully, but these errors were encountered:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
erickoledadevrel commented Aug 27, 2018
Did you download the credentials.json file using the button in the quickstart? Please check that it has an «installed» key at the root.
pradeep-savitr commented Aug 28, 2018 •
I am getting the following error
any help appreciated.
erickoledadevrel commented Aug 28, 2018
erickoledadevrel commented Sep 19, 2018
Closing due to inactivity.
paulcanning commented Nov 9, 2018
I have this same issue.
I have a credentials.json, but it does not has an ‘installed’ key in it. Also, I’m unsure if my json file is made correctly.
erickoledadevrel commented Nov 9, 2018
Did you use the button on the quickstart page? It should ensure the correct settings are used.
inside83 commented Sep 21, 2020
I used type ‘Web browser’ and got an error
PHP Fatal error: Uncaught InvalidArgumentException: missing the required redirect URI in /root/vendor/google/auth/src/OAuth2.php:675
https://developers.google.com/gmail/api/quickstart/php#troubleshooting says «This code requires an OAuth client ID of type Other» but ‘Other’ isn’t offered as an option in the dropdown menu. 
timcamps commented Nov 24, 2020
I used type ‘Web browser’ and got an error
PHP Fatal error: Uncaught InvalidArgumentException: missing the required redirect URI in /root/vendor/google/auth/src/OAuth2.php:675
https://developers.google.com/gmail/api/quickstart/php#troubleshooting says «This code requires an OAuth client ID of type Other» but ‘Other’ isn’t offered as an option in the dropdown menu.
Make sure you have added the Redirect URI in your Client-ID: 
Also don’t forget to download and replace the credentials.json file after you have made any changes: 
Missing redirect uri in request
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
youngda commented Jan 24, 2018 •
No description provided.
The text was updated successfully, but these errors were encountered:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
akshar001 commented Mar 13, 2018 •
Go in to src/server.php find redirect_uri exact match setting it is true turn it to false and try again
gabeblack commented May 3, 2018
But I still get the same error.
gabeblack commented May 3, 2018
SetEnvIf Authorization «(.*)» HTTP_AUTHORIZATION=$1
in order to get the token.php to work per the install guide. (I was running in to the issue reported here: #925 )
gabeblack commented May 3, 2018
I guess my issue wasn’t the same. My error had: «#section-3.1.2» in it.
I found that portion of the code that referenced that section and changed the code to display the expected/measured uri and found that expected uri is what I put in for the INSERT command following the instructions on the step-by-step guide prior to trying it out on the google oauth2 playground:
Авторизация Google OAuth 2-Ошибка: несоответствие uri перенаправления
на сайте https://code.google.com/apis/console я зарегистрировал свое приложение, настроил сгенерированный идентификатор клиента: и Ключ в мое приложение и попытался войти в систему с помощью Google. К сожалению, я получил сообщение об ошибке:
что значит это сообщение и как я могу это исправить? Я использую камень omniauth-Google-на что OAuth2.
26 ответов
URI перенаправления (куда возвращается ответ) должен быть зарегистрирован в консоли API, и ошибка указывает, что вы не сделали этого или не сделали это правильно.
перейдите к консоли для вашего проекта и посмотрите в разделе доступ к API. Вы должны увидеть свой идентификатор клиента и секрет там, вместе со списком URI перенаправления. Если нужного URI нет в списке, нажмите кнопку Изменить параметры и добавьте URI в список.
в моем случае это был www и non-www URL-адрес. Фактический сайт имел www URL и Авторизованный Перенаправление URIs в консоли разработчика Google было non-www URL-адрес. Следовательно, было несоответствие в перенаправлении URI. Я решил это, обновив Authorized Redirect URIs в консоли разработчика Google для www URL-адрес.
другие общие несоответствия URI:
вот пошаговые скриншоты консоли разработчика Google, так что это было бы полезно для тех, кто получает его трудно найти страницу консоли разработчика для обновления перенаправления URIs.
Если вы используете кнопка Google + javascript, то вы должны использовать postmessage вместо фактического URI. Мне потребовался почти целый день, чтобы понять это, так как документы Google по какой-то причине не ясно заявляют об этом.
Missing required parameter: redirect_uri with passport-google-oauth
Using passport-google-oauth: «0.2.0» in my MEAN Stack application (found here: https://github.com/jaredhanson/passport-google-oauth). When I run the application and attempt to sign in with a Google API this error is returned
Missing required parameter: redirect_uri
Request Details scope=https://www.googleapis.com/auth/plus.login response_type=code redirect_uri= client_id=xxxx-xxxx.apps.googleusercontent.com
The redirect param is here passport-init.js
var GoogleStrategy = require(‘passport-google-oauth’).OAuth2Strategy;
var GOOGLE_CLIENT_ID = «xxx-xxx.apps.googleusercontent.com»; var GOOGLE_CLIENT_SECRET = «xxxx»;
passport.use(new GoogleStrategy( <
clientID: GOOGLE_CLIENT_ID,
clientSecret: GOOGLE_CLIENT_SECRET,
callbackUrl: «http://127.0.0.1:3000/auth/google/oauth2callback» >, function(accessToken, refreshToken, profile, done) < done(null,profile); >));
The routes are here authenticate.js
I am sure I am missing something simple, but I don’t know what to add in this question that will give you the best information. Please ask and I will do my best to answer you. This is what feels like the pertinent data.
Funny thing is if I add the callbackUrl manually then everything works great. I can reach the Google API fine. Then I am given the choice to «allow» or «deny» the request.