使用express sever,passport.js进行twitter身份验证后,req.user未定义

时间:2016-04-02 20:47:13

标签: javascript node.js express twitter passport.js

有许多问题与社交认证后获取req.user未定义有关,但我发现没有任何可以帮助我。

我已成功使用示例使用护照进行twitter身份验证:https://github.com/passport/express-4.x-twitter-example。我试图尽可能地遵循这种模式,但似乎无法使其发挥作用。

具体来说,我能够成功进行身份验证,但req.user未定义。这对我没有意义,因为我的用户数据返回没有问题。

我不倾向于认为这是一个中间件问题(就像其他人一样),因为中间件与示例中使用的相同。它可能是关于拥有多个域的东西,但我不确定是什么。所有这些都是在localhost上完成的。

在Twitter中,该应用程序已设置为 网站是:127.0.0.1:3000 / signin 和 回调网址是:127.0.0.1:2999 / auth / twitter / return

正如您所知,我的客户端正在使用端口3000,它正在调用在端口2999上运行的服务器。

为了简要介绍代码,127.0.0.1:3000/signin上的客户端有一个链接到127.0.0.1:2999/auth/twitter的按钮,从而启动身份验证请求。在引擎盖下,快速服务器在server / index.js - server中创建。这会导入routes / index.js中的路由,其中​​一些是控制器authenticate.js处理的。如您所见,oauth twitter请求在authenticate.js中生成。再次,身份验证成功进行,我被重定向到127.0.0.1:3000/search。但是,正如你在this.twitter_callback中看到的那样,我正在打印req.user并且它是未定义的。

请注意,我已经从我的代码中修改了消费者密钥/密钥。

服务器/ index.js

var cors = require('cors')
var bodyParser = require('body-parser')
var express = require('express');
var app = express();
var http = require('http').Server(app)
var io = require('socket.io')(http)
// NOT SURE WHY I NEED TO GO BACK 3 FOLDERS TO GET TO PORT_CONFIG
var port = require("../port_config.json").server_port;
var PORT = Number(process.env.PORT || port);
var routes = require('./routes/index.js')
var database = require('./database/db.js')
var db = new database()

app.use(cors()); // middleware that allows cross-platform requests
app.use(bodyParser.json());

db.dbConnect(function(err,db_instance){
    // routes
    routes(app, db_instance, io)
    // send user polls on connection 
    // TEMPORARY (WILL BE GRABBED ON LOGIN)
    var user = null // WILL BE SET AFTER LOGIN
    io.on('connection', function(socket) {
    var places_attending = db_instance.collection('places_attending')
    places_attending.find({}).toArray(function(err,docs){
        var places_user_attending = docs.map(doc => {
            if (doc.attending.indexOf(user) !== -1) {
                return {
                    id: doc.id,
                    name: doc.name,
                    num_attending: doc.attending.length
                }
            }
        })
        socket.emit('places_user_attending', places_user_attending);
    })
    })
})

http.listen(PORT, function () {
    console.log('Backend server listening at http://localhost:' +     PORT);
})

module.exports = http

路由/ index.js

var Search = require('../controllers/search.js')
var Add = require('../controllers/add.js')
var Authenticate = require('../controllers/authenticate.js')


module.exports = function(app, db, io) {
    var search = new Search(db, io)
    var add = new Add(db, io)
    var authenticate = new Authenticate(app)

    app.route('/api/search')
        .post(search.search_yelp)

    app.route('/api/add')
        .post(add.add_attendee)

    app.route('/auth/twitter')
        .get(authenticate.twitter_authentication) 

    app.route('/auth/twitter/return')
        .get(authenticate.twitter_callback)
}

authenticate.js

function authenticate(app) {

var passport = require('passport');
var Strategy = require('passport-twitter').Strategy;


// Configure the Twitter strategy for use by Passport.
passport.use(new Strategy({
    consumerKey: REDACTED,
    consumerSecret: REDACTED,
    callbackURL: 'http://127.0.0.1:2999/auth/twitter/return'
  },
  function(token, tokenSecret, profile, cb) {
    // In this example, the user's Twitter profile is supplied as the user
    // record.  In a production-quality application, the Twitter profile should
    // be associated with a user record in the application's database, which
    // allows for account linking and authentication with other identity
    // providers.
    return cb(null, profile);
  }));


// Configure Passport authenticated session persistence.
passport.serializeUser(function(user, cb) {
  cb(null, user);
});

passport.deserializeUser(function(obj, cb) {
  cb(null, obj);
});


// Use application-level middleware for common functionality, including
// logging, parsing, and session handling.
app.use(require('morgan')('combined'));
app.use(require('cookie-parser')());
app.use(require('body-parser').urlencoded({ extended: true }));
app.use(require('express-session')({ secret: 'keyboard cat', resave:     true, saveUninitialized: true }));

// Initialize Passport and restore authentication state, if any, from the
// session.
app.use(passport.initialize());
app.use(passport.session());

this.twitter_authentication = passport.authenticate('twitter')

this.twitter_callback = (
  passport.authenticate('twitter', { failureRedirect: 'http://127.0.0.1:3000/signin' }),
  function(req, res) {
       console.log('REQ.USER OBJECT: ' + req.user)
       res.redirect('http://127.0.0.1:3000/search');
   }
)

}

module.exports = authenticate

非常感谢任何帮助。

1 个答案:

答案 0 :(得分:0)

问题在于如何指定我的twitter_callback路由。

如果我将回调更改为:

this.twitter_callback = app.get('/auth/twitter/return',
passport.authenticate('twitter', { failureRedirect: 'http://127.0.0.1:3000/signin' }),
function(req, res) {
console.log(req.user)
res.redirect('http://127.0.0.1:3000/search');
})
一切正常。我认为这与我编写它的初始方式没有正确应用的中间件有关。我不确定如何重写它以导出它,而不使用twitter_callback中的app.get