Angular 5登录模块Passport Local Strategy及authenticate函数失效求助

Hey there! Let's troubleshoot your Passport Local Strategy issue step by step—no console errors but always getting null back is definitely frustrating, but we can narrow this down. Here are the key areas to check:

First, double-check your user collection in MongoDB:

• Make sure users are stored with the correct field names (e.g., if your strategy uses usernameField: 'email', your docs must have an email field, not userEmail).
• Confirm passwords are properly hashed (if you're using bcrypt or similar). If you're storing plaintext passwords, your comparison logic will fail silently.
• Manually run a MongoDB query (like db.users.findOne({ email: 'test@example.com' })) to confirm the user you're trying to log in with actually exists in the database.

Your strategy's callback function is where most silent failures happen. Look for these common issues:

• Are you calling the done callback correctly? For example:

  passport.use(new LocalStrategy({
    usernameField: 'email', // Match this to your request payload and DB field
    passwordField: 'password'
  }, (email, password, done) => {
    // Add console logs here to debug
    console.log('Attempting to authenticate user:', email);
    
    User.findOne({ email: email }, (err, user) => {
      if (err) return done(err); // Don't forget to pass errors to done!
      if (!user) return done(null, false, { message: 'User not found' });
      
      // Check password match (example with bcrypt)
      bcrypt.compare(password, user.password, (err, isMatch) => {
        if (err) return done(err);
        console.log('Password match result:', isMatch);
        if (isMatch) {
          return done(null, user); // Success: pass the user object
        } else {
          return done(null, false, { message: 'Invalid password' }); // Failure: pass false
        }
      });
    });
  }));
  

• Did you accidentally pass null instead of false in the done callback when authentication fails? That could lead to unexpected null returns.

Make sure your login route is configured properly:

• Are you handling the authentication result explicitly? If you don't provide a callback, Passport might send a default response that you're not expecting. Try adding a route handler like this:

  router.post('/login', (req, res, next) => {
    passport.authenticate('local', (err, user, info) => {
      if (err) return next(err);
      if (!user) return res.status(401).json({ message: info?.message || 'Authentication failed' });
      // If successful, generate tokens or send user data here
      res.json({ user: user });
    })(req, res, next);
  });
  

• Confirm you've initialized Passport in your Server.js:

  const passport = require('./path/to/passport');
  app.use(passport.initialize());
  // Only add this if you're using sessions:
  // app.use(passport.session());
  

Since there are no console errors, manual logs will be your best friend:

• Log the request payload in your login route: console.log('Request body:', req.body) to confirm you're receiving the correct username/email and password.
• Log the result of User.findOne in your strategy to see if a user is being fetched from the DB.
• Log the password comparison result to rule out hash mismatches.

Ensure your Angular frontend is sending the request with the correct content type (application/json) and that the payload keys match what your strategy expects. For example, if your strategy uses usernameField: 'email', your frontend should send { email: 'user@example.com', password: 'xxxx' }, not { username: 'user@example.com', ... }.

If you can share snippets of your actual Passport.js, Server.js, user model, and login route code, we can spot more specific issues!

内容的提问来源于stack exchange，提问作者AQ Hassaan