Databases
StackOverflow2013
Postsdbo
POHow to do asynchronous authentication in Node.js + MongoDB + PassportJS app
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to do asynchronous authentication in Node.js + MongoDB + PassportJS app
    primarykey
    data
    text
    <p>I'm using Node.js, MongoDB, and PassportJS and I'm trying to authenticate using the local strategy (just simple id and password). The problem is that everything in Mongo is asynchronous, but Passport is synchronous. I thought about trying to "hook" passport so that I could create my own callback to continue with authentication once the Mongo callbacks returned, but I don't know how the passport code works (and I'm not yet desperate enough to fire up a debugger and trace it).</p> <p>The authentication process will actually finish successfully, but not before the app has responded to the client, causing the client to think it is still un-authenticated. For example, after the client tries to authenticate, it is redirected back to the login form because the session isn't authenticated. If I then simply refresh the page, I get in because, by that point, the authentication callbacks have returned.</p> <pre><code>passport.use(new localAuth(function(username, password, done) { process.nextTick(function() { mc.connect('mongodb://127.0.0.1:27017/example', function(err, db) { if(err) throw err; db.collection('users').findOne({GUID: username}, function(err, results) { if(err) throw err; console.log('Here I am!'); db.close(); return done(null, username); }); }); }); })); </code></pre> <p>(I realize the above code is not authenticating anything. I'm just trying to work through the asynchronous approach.)</p> <p>I've tried multiple different variations on the above, but they all suffer from the same issue: the function given to <code>localAuth()</code> returns and passport proceeds with authentication before my database lookup has a chance to complete. I've seen several questions on SO about trying to force mongo to work synchronously and the responses are all <em>"don't"</em>. I saw this <a href="https://stackoverflow.com/questions/12639476/passport-js-authenticate-users-from-mongodb-with-passport-local">question</a>, which is exactly my scenario and my approach is the same, but I still have the issue of needing to refresh after the callbacks return.</p> <p>How should I perform authentication in a node.js + mongoDB + passport app?</p> <p><strong>UPDATE</strong> I have noticed that 'Here I am!' appears in the log during the first attempt (ie. prior to refreshing the page). That makes me think that authentication is finishing and the session is set during the first authentication attempt. Just whatever is being returned from <code>localAuth()</code>'s callback (<code>done()</code>) isn't making it in time. Then when I refresh, passport tries to get the session and sees that it's there. This brings me back to trying to hook passport. Does anyone know when <code>new localAuth()</code> gets called during authentication?</p> <p><strong>UPDATE</strong></p> <pre><code>function authenticateUser(id, pass, cb) { console.log('1'); mc.connect('mongodb://127.0.0.1:27017/sp2010sec', function(err, db) { if(err) throw err; console.log('2'); db.collection('users').findOne({GUID: id}, function(err, results) { if(err) throw err; console.log('3'); return cb(err, id); }); console.log('4'); }); console.log('5'); } passport.use(new localAuth(function(username, password, done) { console.log('6'); authenticateUser(username, password, function(err, user) { console.log('7'); return done(err, username); }); console.log('8'); })); </code></pre> <p>The above code produces this log:</p> <p>6</p> <p>1</p> <p>5</p> <p>8</p> <p>2</p> <p>4</p> <p>3</p> <p>7</p> <p>Passport does not appear to be waiting for <code>done</code> to be called.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAllen
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload