Troubles using "usernameField" to set another username about passport-local-mongoose HOT 5 CLOSED

You could try the new 0.2.1 version that was just published (with undocumented features). This version adds a "createStrategy" static model method that can be used to create a configured LocalStrategy instance.

From 0.2.1 on you can use this code to configure passport

var Account = require('./models/account');

passport.use(Account.createStrategy());

passport.serializeUser(Account.serializeUser());
passport.deserializeUser(Account.deserializeUser());

Passing options to passport-local strategy is done in the createStrategy static method.

from passport-local-mongoose.

+1

from passport-local-mongoose.

Hi,

passport-local-mongoose does only care about the model side of authorization. So when you configure passport-local-mongoose with a field "email" as usernameField then passport-local-mongoose takes care that this field is used when for example authorize() get's called by passport. The mapping part of the form input from req.body to the authorize() method is done by passport-local. And passport-local has no knowledge about the model mapping. So you have two choices to solve this issue:

1. Configure passport-local's LocalStrategy to the same usernameField as configured in the passport-local-mongoose model
2. Use the name "username" in your login form as input name

The current situation a bit to complicated and confusing. I'm thinking about a solution to integrate passport-local and passport-local-mongoose a bit better...

from passport-local-mongoose.

I took a look at the code and figured out. Thanks!

from passport-local-mongoose.

Fixed in 0.2.1

from passport-local-mongoose.