JWT Route Protection | Creating a REST API with Node.js 

Thank you very much for this amazing feedback! I'll try my best to keep it going :)

Thank you very much for this great feedback Robert!

And I'm so happy to have you on board of the channel Nico! Thank you so much for your absolutely amazing feedback, it really means a lot to me to get such a support, thank YOU :)

Wow, getting such a feedback for a RU-vid series is simply awesome, thanks a lot James!

That's true - I'm so used to setting headers manually, I never even had a closer look at that option :D

Academind :)

if you use that Authorization, how to read the token in our code then?

how do i do that mine is doing the same

no shit :P

@Adeshpal Singh You have the user ID in the verified and decoded token. Therefore use that to restrict which data elements can be affected.

damn :D i was thinking the same thing during the entire video and was confused as hell like as "what if there are many users"?.. thanks man

I have another question (related) - isn't the "Bearer" part handled by JWT package if it's the way to go? Splitting it manually doesn't look good.

Thanks so much Harshil, that's really awesome to hear! :)

It's really great to read that the video was helpful Tim, thanks so much for sharing this!

New token will be created if you call login route again

We requested it already, thank you for the hint and for your great feedback Sachin :)

Thanks for the suggestions! I can't promise anything, I might look into these things in future series though

So cool to read that Lucas, thanks so much! YOU are the best, greetings from Germany :)

Just fantastic to read that Camilo, thank you very much for sharing this!

Very cool to read that Imad, thank you very much for your comment :)

I am getting that error as well, did you find out the answer?

Wow, thank you so much for your absolutely amazing feedback Anshul. What more can I say but THANK YOU, it really means a lot to me to read that :)

Thank YOU for your awesome feedback, so happy to read that you like what I'm doing here :)

Thanks for the very nice feedback and the suggestion! I might add a frontend, we'll see :)

Thanks so much for sharing this Liston. It really means a lot to me to read that the videos are helpful :)

I also implemented my solution like that. It is very good in terms of avoiding redundancy. Nevertheless, sometimes you want protect a route, in which also the login method is located. So you may have to protect each specific subroute individually because otherwise you will not be able to access the login method anymore.

YOU are awesome, thanks so much for your comment!

So happy to read that the video is helpful Leonardo! Wish you all the best for your project :)

So cool to read that Federico, thanks a lot for sharing this!

Same problem here, Did you find the solution yet?

Well, Found a solution I guess. Just add an image with the ProductImage parameter, with the name and the price and it works

@@masterman4953 It doesnot work,

For me the issue was that I had two next() calls in the check-auth.js when there should only be one after the catch block

Thank you, I also wish you a happy new year Anand :)

So great to read that Edison, thank you for sharing this!

Thank you very much for your support Ulises, so happy to have you on board of the courses and to read that you like my explanations :)

I guess you can't store cookies when accessing API using a mobile client.

Very happy to read that you like it Hadyan, thank you for your comment!

Thank you Tom!

Happy to hear you liked it! I only worked with Passport and found it to be quite good :)

Academind Great! Thank you again!

The token contains encoded payload data. In the previous video you can see he put the email and userId in the payload data. So when he verifies the token, the decoded payload data will return. In his case it is the email and userId, which is user data. To be able to easily access this user data in the endpoints that use authentication he puts it in the req variable.

You should add the bearer, too

I'll certainly dive into Laravel again in the future, yes :)

Thank you ver much Max)) You are inspired me to coding!!!

use this website to post the code: hasteb.in then post the link witht the code in under your youtube comment. Tag me, so i get notified

@RANDOM.mp4

@@I_hu85ghjo hasteb.in/epufojep.js

I've got the same problem

For me the issue was that I had two next() calls in the check-auth.js when there should only be one after the catch block

YOU are the best, thank you very much for your amazing feedback, so happy to read that :)

Node.js supports next-gen JS - that's why I use it. let and const are part of that

I googled for "ajax" and "send token" (and "Vue") and found some good instructions.

Thanks for the very nice feedback and the suggestion! It's on the "idea list", can't promise if/ when I'll get around doing it though

What exactly do you mean with "change the route"? Normally you would of course connect via JS

Thanks for the answer, Max. app.post('/verifyheader', (req, res)=>{ console.log(req.headers); if(req.headers['my-token'] === "abcdefghijklmnopqrstuvwxyz"){ res.send("Token verified"); }else{ res.send("error"); } }); At console.log(req.headers) the token arrives, but then It doesn't execute res.send("Token Verified") to change the page var btn = document.getElementById('butx'); btn.addEventListener('click', function(e){ e.preventDefault(); var XHR = new XMLHttpRequest(); XHR.open("post", "/verifyheader"); XHR.setRequestHeader('my-token', 'abcdefghijklmnopqrstuvwxyz'); XHR.send(); });

Thanks for the suggestion Anurag! GraphQL is something I might cover but I can't tell when I'll be able to release some content on it