Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've gotten a band-aid over the asynchronous authentication, so I'll explain what I did. If anyone can give a better answer, I'd love to hear it.</p> <p>So, the problem is that mongoDB is asynchronous, but passport is not and everything I could think of resulted in passport authenticating the request (or failing to, rather) before the mongo callbacks had returned. I tried multiple approaches to hooking passport so that I didn't even start the passport authentication until I had the mongo stuff done (sort of pre-authentication), but that didn't work either. I'm assuming that has to do with the internals of passport.</p> <p>What I ended up doing was opening the db connection at app startup and leaving it open for the life of the app. This cuts down on one callback and I think this is letting the mongo callbacks finish in time for passport to see it. <strong>This feels like a potential race condition.</strong> I would love to see a better answer than this or an explanation as to what's really happening.</p> <p><strong>UPDATE</strong></p> <p>The real problem was that I wasn't using passport's success/failure redirects; I was handling that on the client side, which started as soon as the AJAX call returned (but was not involved in the passport callback chain). Once I started handling the redirects on the server side, the authentication started working as expected/advertised.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to do asynchronous authentication in Node.js + MongoDB + PassportJS app
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAllen
    1. USAllen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to do asynchronous authentication in Node.js + MongoDB + PassportJS app
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPassport supports asynchronous operation, that's why it passes the `done` callback function which you're supposed to call once your (async) user check is finished. There *is* a potential race condition with opening the database at app startup, but you can always wait for the database to connect before starting to accept incoming requests to your Express application.
      singulars
      1. PO
      1. USrobertklep
    2. COThe problem was that the callbacks weren't finishing in time--so I open the db connection early to remove one of the callbacks that must finish. But what if `findOne` takes longer than normal? I think I could end up in the same situation as before. In the code above, `done` is called in the last callback (as you suggest), but after much testing I have seen that passport does not wait for this. As soon as `mc.connect` finishes, passport moves on. It does finish, which is why the second request (when I refresh the page) gets authenticated. I've added an additional example to the question
      singulars
      1. PO
      1. USAllen
    3. COI think you're missing the finer nuances of asynchronous execution: when an async function is called, execution of the code following that call will continue. Passport won't (or rather: *can't*) wait for an async function to finish before continuing, therefore it passes a callback which will be called when the async function is done. In your example: you can't expect #8 to be logged last, because any of the async functions can finish later.
      singulars
      1. PO
      1. USrobertklep
 

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