CODEWITHSUNDEEP
node.jsexpressgoogle-oauthpassport-google-oauth
Trewaters
Trewaters

Reputation: 1069

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

  1. That’s an error.

Error: invalid_request

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

router.get('/google', passport.authenticate('google', { scope: ['https://www.googleapis.com/auth/plus.login']}), function (req, res){ });

router.get('/google/oauth2callback', passport.authenticate('google', { successRedirect: '/auth/success', failureRedirect: '/auth/failure' }) , function (req, res) {res.redirect('/');} );

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.

Upvotes: 11

Views: 35103

Answers (6)

Yoko Hailemariam
Yoko Hailemariam

Reputation: 37

In my case i had to restart the server after writing callbackURL inside my .env file

Upvotes: 0

Tyler Momoh
Tyler Momoh

Reputation: 43

I had this issue to. in my nestJs Application. I solved it by changing the CallbackURL from "callbackUrl" to "callbackURL" URL all caps

Upvotes: 1

André Santos
André Santos

Reputation: 11

My issue occuors in authenticate with WSL. This error bellow is presented:

error issue

To solved , utilize the command gcloud init --console-only in your terminal.

Upvotes: 0

Saurabh Chaubey
Saurabh Chaubey

Reputation: 11

I use something like that- 1. Make sure that's URL and not uri. 2. Make sure the callback URL you registered is same as the one you are requesting for.

var passport = require('passport');
var GoogleStrategy = require('passport-google-oauth').OAuth2Strategy;

// Use the GoogleStrategy within Passport.
//   Strategies in Passport require a `verify` function, which accept
//   credentials (in this case, an accessToken, refreshToken, and Google
//   profile), and invoke a callback with a user object.
passport.use(new GoogleStrategy({
    clientID: GOOGLE_CLIENT_ID,
    clientSecret: GOOGLE_CLIENT_SECRET,
    callbackURL: "http://www.example.com/auth/google/callback"
    //should be same as the one you registered in credentials.
  },
  function(accessToken, refreshToken, profile, done) {
       User.findOrCreate({ googleId: profile.id }, function (err, user) {
         return done(err, user);
       });
  }
));

P.S:my first one on stackoverflow. please ignore mistakes and help me in improving.

Upvotes: 1

Philip Huysmans
Philip Huysmans

Reputation: 256

When defining the GoogleStrategy, the JSON key should be callbackURL instead of callbackUrl (i.e., capital URL). Had this 'issue' as well ;-)

Upvotes: 24

Meir
Meir

Reputation: 14365

I have a working example using the same strategy. Since I don't get this error, can't pinpoint what the problem is, but I wanted to suggest you check the following:

  • add to your google strategy creation (new GoogleStrategy({...})) the scope:

    scope: 'https://www.googleapis.com/auth/userinfo.email',

  • Make sure your google api is configured properly in the dev api console. Specifically:

    1. Under APIs and auth | Credentials | OAuth consent screen - all the required url.
    2. Under APIs and auth | Credentials - look for your web api client and see you authorized all the relevant URIs. The auth will not work if the call is from or the redirection is to a page that was not listed in this section.

Upvotes: 1

Related Questions