Passport is Express-compatible authentication middleware for Node.js.
Passport's sole purpose is to authenticate requests, which it does through an extensible set of plugins known as strategies. Passport does not mount routes or assume any particular database schema, which maximizes flexibility and allows application-level decisions to be made by the developer. The API is simple: you provide Passport a request to authenticate, and Passport provides hooks for controlling what occurs when authentication succeeds or fails.
$ npm install passport
Passport uses the concept of strategies to authenticate requests. Strategies can range from verifying username and password credentials, delegated authentication using OAuth (for example, via Facebook or Twitter), or federated authentication using OpenID.
Before authenticating requests, the strategy (or strategies) used by an application must be configured.
passport.use(new LocalStrategy(
async (username, password, done) => {
try{
const user = await UserModel.findOne({username : username}).exec();
// here is where you make a call to the database
// to find the user based on their username or email address
if(!user){ //check for users existence
return done(null,user, {message: 'Invalid username or password'});
}
const passwordOK = await user.comparePassword(password); //compare password
if (!passwordOK) {
return done(null, false, { message: 'Invalid username or password' }); //not found. Send the error message to callback
}
return done(null, user); //return user to callback
}catch(err){
return done(err);
}
}
));For detailed usage check Main.js file
There are 480+ strategies. Find the ones you want at: passportjs.org
Passport will maintain persistent login sessions. In order for persistent sessions to work, the authenticated user must be serialized to the session, and deserialized when subsequent requests are made.
Passport does not impose any restrictions on how your user records are stored. Instead, you provide functions to Passport which implements the necessary serialization and deserialization logic. In a typical application, this will be as simple as serializing the user ID, and finding the user by ID when deserializing.
passport.serializeUser(function(user, done) {
done(null, user.id);
});
passport.deserializeUser(function(id, done) {
User.findById(id, function (err, user) {
done(err, user);
});
});Passport provides an authenticate() function, which is used as route
middleware to authenticate requests.
app.post('/login', passport.authenticate('local', { successRedirect: '/',
failureRedirect: '/login' }));Passport has a comprehensive set of over 480 authentication strategies covering social networking, enterprise integration, API services, and more.
There is a Strategy Search at passportjs.org
The following table lists commonly used strategies:
| Strategy | Protocol | Developer |
|---|---|---|
| Local | HTML form | Jared Hanson |
| OpenID | OpenID | Jared Hanson |
| BrowserID | BrowserID | Jared Hanson |
| OAuth 2.0 | Jared Hanson | |
| OpenID | Jared Hanson | |
| OAuth / OAuth 2.0 | Jared Hanson | |
| OAuth | Jared Hanson | |
| Azure Active Directory | OAuth 2.0 / OpenID / SAML | Azure |
- For a complete, working example, refer to the example that uses passport-local.
- Local Strategy: Refer to the following tutorials for setting up user authentication via LocalStrategy (
passport-local):- Mongo
- Express v3x - Tutorial / working example
- Express v4x - Tutorial / working example
- Postgres
- Mongo
- Social Authentication: Refer to the following tutorials for setting up various social authentication strategies:
- Express v3x - Tutorial / working example
- Express v4x - Tutorial / working example
- Locomotive — Powerful MVC web framework
- OAuthorize — OAuth service provider toolkit
- OAuth2orize — OAuth 2.0 authorization server toolkit
- connect-ensure-login — middleware to ensure login sessions
The modules page on the wiki lists other useful modules that build upon or integrate with Passport.