Walkthrough: Using Passport Local Strategy

[kunmiamzat]

Okay, this is very enlightening. If I don't drop a comment, the universe is gonna get angry with me. Thanks!.

[Samsul]

This guy is a non-mono tone instructor. He knows how to deliver the teaching materials in a pragmatic and creative styles.

[Sengi]

ngl I have watch tons of video about passport local, this video's explanation was the best, he gave all concepts I wanted to know, those all of messy passport setup and configure things

[ΑρηςΕμπαντα]

The best tutorial in the universe! Thanks man!

[pini]

Thank you very much for the clear explanation.

[Toojool]

Im not going to understand everything a youtuber shows in their videos on how to do something, there are so many ways to do one thing, but how this guy explains how hes doing his way was very helpful and his enthusiasm helps as well

[als]

Man this is the best local strategy video i've seen. Good work dude.

[naderabdelrahman]

You explained that very well.
You have a gift, please keep up the great work!

[Yogesh-krbo]

afaik side effect import is now a vanilla feature too... btw awesome tutorial

[bradenmitchell]

Great video! However, something I've learnt recently is that you don't need to implement the passport.serializeUser() and passport.deserializeUser() functions unless you are utilising sessions. Since you're using JWTs in this project, the two functions are not needed. Instead, when you use the 'passport.authenticate()' function to protect a route, you can pass in a second configuration object that tells passport that you're not using sessions, e.g. passport.authenticate('local', { session: false }) or passport.authenticate('jwt', { session: false }). If you don't set session to false, passport will expect the serialise and deserialise functions to be defined and will throw an error if they aren't.

[AveNers]

Finally found a tutorial using TypeScript and async/await instead of ugly callbacks

[deanchanghuber]

God bless you, the documentation didn't explain what was going on so well and other tutorials were a snooze fest.

[anasouardini]

you make it feel like passportjs done everything for you(a developer), but you haven't realized that you did everything yourself and all what passport did is almost 20%.
why people even bothering to use it?

for me, it seems a very bad idea to import a whole library just to abstract two lines of code :)

my opinion is that it handles stuff for you, but with the same amount of code that you could've written yourself, and I think that's why people think it's helping at something.