$ npm i passport $ npm i express-session // Install the primary 'Passport JS' library, and the 'express-session' library // The main 'passport' library piggybacks on the 'express-session' library, so in order to use 'passport' you will have to install 'express-session.Īuthentication Library: The secondary library is used for authenticating the users. Its sole purpose is to maintain (attach) the (already authenticated) user to sessions. The main Passport JS library deals with already authenticated users, and does not play any part in actually authenticating the users. Passport JS: The “Passport JS” library connects with the “expression-session” library, and forms the basic scaffolding to attach the (authenticated) user information to the req.session object.

“passport-local” or “passport-facebook” or “passport-oauth-google” etc.) The Passport JS framework abstracts the Login process into 2 separate parts, the “session management” (done by the “Passport JS library” ), and the “authentication” (done by the secondary “Strategy” library eg. “passport-local”, “passport-facebook”, “passport-oauth-google” etc.

The secondary “strategy” library is dependent on the methodology you plan use to authenticate a user.

you will import this library irrespective of the type of “Strategy” that you will use to authenticate the user).

The primary “Passport JS” library is always required, and is used to maintain session information for authenticated users (i.e.

The first is the main “Passport JS” library, and the second is the relevant “strategy” library. It is important to understand that the Passport JS framework, consists of 2 separate libraries.

Passport js