request object in express server does not persist
<p>I am using passportjs (google/facebook strategy) to login. What I observed is that the req.session (from express-session) is updated with 'passport.user' key after logging in via the social channels (using serialize user). This is fine.</p>

<p>What I expected was that if the next http request is made then in that the req.session would still contain the passport.user key, but that does not happen. So I had to store the session in mongodb via mongo-connect. Now in the mongo store I have the session information present.</p>

<p>Is this normal behaviour? That req object does not persist in between two http request to the same express server instance? So every time a new request has to be made the session has to be retrieved from the mongo store. </p>

<p>It begs the question, if the above behaviour of req.session is true, why do we need deserializeUser ?</p>