node-express-passport | 通过 Passport 去实现登录模块，express-flash 实现页面通知 | Authentication library

I am new to Node and starting with the Rocket Rides demo. The pilot sign-up works on the web app and I want to do the same for passengers on the web (whereas the demo has passenger signup on iOS). I can't understand why the req.user is maintained with the original code for pilots and not my adaptation for passengers.

I added console.log() in the GET of server/routes/pilots/pilots.js:

I have a MERN stack blog app that I'm making as a learning exercise. I'm relatively comfortable on the front end but have limited experience in node. I'm adding authentification after following a couple tutorials to get this far. I'm using passport.js as a framework to make a request to Google, get back an id and save as session info. However, after logging in, req.session is empty when making a post request, even though I can see a cookie in the dev tools.

I'm using bcrypt's hash to obscure the actual id, but that may not be best practice.

in blogAuth.js: req.session is defined.

bcrypt.hash(req.user._id.toString(), saltRounds, function(err, hash) { req.session.user = hash; //session is set here. console.log(req.session); res.redirect(http://localhost:8080/articles/loggedIn); });

but in api/articles.js: req.session is empty

router.post("/", (req, res, next) => { const { body } = req; // session is empty here. Why? console.log(Session user, ${req.session.user}); console.log(req.session);

I have tried:

• Including proxy in the client package.json: express req.session empty with cookie-session

  using withCredentials set to true when sending the POST from the client:Node + Express + Passport: req.user Undefined

  Rearranging the order of middleware: Routes must always come afterward, but I feel like I'm doing this blindly and it usually results in an error

Here's some of the relevant files:

Server side: - app.js - blogAuth.js - passport.js - api/articles.js

Client side: - the POST req

Entire project

I believe this is an issue with ordering. What is a good way to ensure that I order my middleware correctly? Or if the order looks correct, where else could this issue becoming from?

How I can use the Passport's {user} parameter in my route users.js which I already can access through routes.js ?

The case is that I need to access Passport parameters in multiple new route files so I do not have to user routes.js as the only file that contains all my application's routes.

app.js - I am isolating only the parts of interest

My Question is similar to this.I am using express version 4.14.0 and I have implemented OAuth2 SSO using "passport-ping" module. For getting new Access token from refresh token which we have on successful login I am using "passport-oauth2-refresh" module. No problem with these modules. Everything works fine as expected. But the problem is with request.user object. Below is my code