How To Manage User Roles In Node.js

[@cdporgrammer7168]

Man I wonder if Kyle actually realises how much he helps us out with his vids man Respect man

[@MrEnsiferum77]

React kids won't understand u...

[@astkh4381]

@@MrEnsiferum77 реакт тут причем?

[@hnasr]

Legend! Love the way you clearly explain these concepts in a simple way. Cheers bro. You are on my recommended channel list on my YT

[@AmanNidhi]

i recommend you both on mine

[@neon13x]

Legend praising another legend

[@kartikjha833]

This comment section is pretty legendary

[@JD-hq1kn]

Ok

[@taquiyt]

pretty much exactly the video I needed for a project. My man web dev simplified is a legend.

[@cdporgrammer7168]

You get it m8

[@sohailkashif6992]

@@cdporgrammer7168 dear how it connect with mongodb?

[@tyrrelldavis9919]

Very true. He is one of the few "bigger" code KZbinrs that has beneficial stuff I've used in real projects

[@tyrrelldavis9919]

@@sohailkashif6992 a common cope I would get hit with in boot camp was, "Depends on your use case" Which it actually does. Having a hard time understanding the relationship between a user of the database And A user that is using the site.

[@ng4logic]

this dude is literally a mentor

[@mrsmasked180]

You're simply the best out there because you explain your content very well and you go straight to the point, respect man you're a legend !

[@pprathameshmore]

Before watching this video, I was creating separate documents for admin and user. Thank you for such a clear explanation tutorial.

[@sandVidz]

I did that and submited lol. Had to pay for that in viva.

[@NorteXGame]

Never happier when any youtuber uploads

[@riadhossain4020]

Kayel your videos are greate for intermediat developers. Clear and simple explanations. Have been following you. You are recommended.

[@bedrockcoder5169]

*Kyle *great *intermediate

[@jmmacatangay_grizzlybear]

I always keep telling everyone to subscribe to your channel. you're really great really hoping people would recognize you more often.

[@ayoubalem865]

7:11 Th res.Status Should be 401 Not 403 401 Means Unauthorized , Forbidden Mean He is Sign Up But he doesn't have the permission to access to the given operation. Thank You btw !

[@Study-bt6qh]

kakashi hatake😍😍

[@tranquility6358]

I believe you mixed up the status codes a bit. 401 Unauthorized - send this code when the user is not authorized to view the content (as in the user didn't login) 403 Forbidden - send this code when the user is logged in, but is not allowed to view specific content The difference between these status codes is that 401 should be sent if authorization fails, but proper authorization is possible while 403 is sent when the user is authorized, but doesn't have the required permissions.

[@cheetahBeachwood]

are you sure? authentication means verifying identity. It gets confusing because the header used to authenticate is called 'authorization' but it is still authentication and 401. authorization means verifying permissions which is 403

[@brielov]

I agree... 401 is for unauthorized (not logged in) and 403 is forbidden (resource authorization)

[@Hadermite]

@@cheetahBeachwood Yes, he's correct. The title of the status code is a bit messed up, should probably have been "Unauthenticated" instead, it generates a lot of confusion.

[@andrejvujic]

@Jovan Jevtic jovaneeeee

[@eduardonunes1379]

This video is so motivating since I was taking a break from programming bc of authentication and authorization. Thank you so much!

[@ridl27]

such a clear explanation, thank you!

[@pavelsokolov4190]

Currently I'm learning MEAN and this is exactly what I need for my pet project. Thank you so much for what you're doing!

[@ginokoybi7010]

Your video help me too much thanks 🙏

[@LabhamJain]

You've Successfully Simplified Web For Us. Mission Accomplished 😎

[@kmparkhu]

Yay!!!!!!!!!!!!!!!!!!! So awesome!!! Thank you !!!! I was just thinking about this because I been following your other tutorials and I love them. I am excited to watch this video.

[@T3kKeN9]

Awesome video. Concept of modularity with pure functions make this truly scalable.

[@MatteoScano]

Thank you very much. This video... no, all your videos I watched are amazing and helpfull!

[@evanmcdaniel5544]

Thanks so much for this. One of the better Node tutorials I've seen.

[@jacob.lee380]

Every time I get stuck in something and try to solve a problem by myself. I'm always ended up on your video finding a solution

[@jeffmair]

Your tutorials are top notch Kyle!

[@HashimWarren]

Love the progression in this video. Super clear

[@pedro_jaber9357]

OMG! thank you. I believe in Web Dev Simplified supremacy!!!!!

[@swibay]

My name is Kyle and my job is to simplify the web for you! Your tutorials are always gre8!

[@ononaokisama]

Literally god tier content

[@joel9909]

Just found your channel, loving it so far.

[@yabu_ai]

This is the best video about role based authentication...Thanks

[@dthoma128]

Kyle ... great tutorial ... very glad I found your channel! Thank you.

[@HurikaneTv]

Kyle ... One Word: Genius

[@rfossella]

As usual, great video - clear, concise and immediately usable. Thanks!

[@stylesoftware]

Awesome, helped me with some of my lingering middleware integration ignorance. Well explained!

[@apurvsawant5703]

Exactly the video I needed. Thanks man.

[@feminjustin2478]

you explain things so simply....easy to follow.....

[@Hrit]

Enjoyed the turotial throughly!

[@taherr1341]

Awesome. You are the best. I wonder who could be so unfair to dislike it?

[@tbg6nb]

20:31 does it make sense in practice ? I'm pretty sure an admin should have right to delete any project

[@sapnilpatel1645]

Your video helps me a lot. I really appreciate your effort. Thank you so much!

[@jodufan8754]

I would recommend to assign every role an int so you can calculate up and downwards ! Edit: To calculate the inheritance of the groups if given!

[@montasirmahmud3585]

Why ? explain briefly please..

[@jodu]

@@montasirmahmud3585 Then you can just use bit calculations to check if a role is hierarchically over another role or not by for example using >=

[@harleyspeedthrust4013]

I've got a permission system where the permissions are strings like "mail.create" or "mail.*". Each user has an array of permissions, and the permission strings are referenced in a POJO that maps object keys to permission names. So if you have an endpoint that should be accessible to anyone with a mail permission, you call `hasAnyPermission(req.user, Permissions.mail)` where Permissions.mail is an object containing more fine-grained permissions, and that endpoint would be accessible to anybody with a "mail.(whatever)" permission. "*" is a wildcard that refers to all sub-permissions, so if someone has the permission "*" then they're a superuser, and if they have the permission "boards.*" then they can do anything on any image board. There are some functions, like `hasAnyPermission` or `hasPermission` that you stick at the beginning of your route handler to enforce the permissions. Of course you don't have to put them at the beginning of your route handler - the entire frontend of the app is handlebars so I also use them on specific pages where I want to display some items/links but each link requires a separate permission. I'm actually pretty surprised that I've made it this far using only handlebars and plain JS for the frontend. The backend is NodeJS with Typescript which is great but I've managed to write a multiplayer FPS almost entirely in plain JS (server-side is that typescript nodejs I just mentioned) and build a forum engine and now I've set up a mail server and a way for users to create and manage email addresses on my domain. handlebars may not be flashy but damn if I like it

[@bilza2023]

why ??? why not use the already available libraries?

[@harleyspeedthrust4013]

@bilza2023 because modern javascript use-libraries-for-everything culture is cancer

[@OnlyJavascript]

please make a complete node course for beginners to intermediate level and an advanced node course too. We are ready to buy it. Please vote if u guys need it too.

[@vinhubcompters]

best teacher ever

[@juliecherner9085]

Thank you for such an amazing tutorial!

[@omar9987]

It would be awesome if you could create like a mini blog[or anything] with react & express that uses user-based roles. I'm trying to add user based rules to my react app :p

[@williamxu2402]

Thank you very much! This is exactly what I needed for my project!

[@adithyasanthosh30]

Nice. Introductory tutorial on how to manage user roles.

[@virgiliogervacioestadillo1389]

Thank you so much Kyle. I found this very helpful.

[@nitindaphale2008]

Very good explained , Love from India.

[@saisaske1]

Just want to say thankyou man. Words are short here.

[@coanjos]

This video came in the perfect time. Thank you!

[@TheBabelian]

wow! such a great tutorial. thanks for the guide!

[@a1225johnny]

very clear, it’s helpful in my project. Thanks a lot

[@thejasong01]

YOU ARE AWESOME thankyou for putting great content, with fast but effective and SIMPLE :)

[@omrimaher2754]

Really amazing explanation!

[@smsibasish]

Great content. Would love to see an elaborated version of this with more of a real world scenarios where an user can have multiple role for different context.

[@WebDevSimplified]

Really all you need to do is make the user.role property an array and then check if the role is in the array or not.

[@smsibasish]

@@WebDevSimplified I feel that will create some problem. Let me explain with your example. Say I introduce two new roles project viewer and project admin. Now one user can be project viewer for one project and project admin for another. If I model my user to have an array of roles then how do I keep track of which project he is an admin of.

[@mrviometal4948]

@@smsibasish I think you can simply tie the role to the project, meaning your DB entry can look like this: Projects: [ { id:1, name:"first project", userId: 1, userRole: canView}, ... ] then you check for the user's role with its id to distinguish between what can be viewed and what can be edited, deleted or updated but what case should require something like that?

[@smsibasish]

@@mrviometal4948 consider this example. A user can be part of many groups and a group may contain a few user. A user can be a admin of few groups but member of other groups. In that case what should be the role of the user in User model and should the Group model have the admin and member fields separately.

[@mrviometal4948]

@@smsibasish I see, I think it can be solved by an abstraction between admin and view. i.e. any admin can view, but not any viewer can be an admin. And so, the edit and delete have to be from an admin or the respective user of the project. But the project entries can contain an array of users who can view...i.e. => Projects: [ { id:1, name:"first project", userId: 1, usersWhoCanView: [2,3,4,5...]}, ... ] so in the implementation of the can view, we can look up the array if it contains the signed-in user's id. In this case, those who can view are (Admins, People who create the project i.e. userId, and any user in the array) Does that make sense?

[@mayank_singh_43]

This is what i want , u are awesome sir 🤘🤘🤘

[@mamusthafa6]

YOu are amazing... Really simplified complex things

[@geld5220]

too good. I did a version in typescript but followed your flows. Thanks

[@user-ww6ns4hn9r]

mmh, i think there is some confusion between permissions and actually filtering the correct data. One thing is permission based on levels (the higher level, the higher the privilege to see things), and one things is to filter the correct projects for the user. wouldn't that be a filter applied at DAO level which returns the right data rather than crammining into the permissions? Permission after all should be agnostic to the kind of data you are handling, and should worry only about roles . correct me if I am wrong?

[@dpolo567]

Thanks for the great tutorial. In the end, I'm just wondering (if we work with real data obtained from the database), what is the best way to filter the data (in this case the scopedProjects function). If we have a lot of data, in this case we need to fetch all of them and then filter them. Isn't it better (in terms of performance) to check the role first and then pull only specific (filtered on db query level) data from the database?

[@mcmuffin1258]

If someone knows someone else's userId there could be problems. How do we make sure someone cant modify userId in the request?

[@zlatan1261]

This is the question that worries me as well

[@navan1087]

use jwt short lived token

[@nirahhp999]

could please create a video on RBAC in MySQL with limited permissions to API in nodejs

[@bulldog2024]

You could have a super admin that would have the ability to delete any project. If an employee is no longer working for the company, you might want to have someone either delete that employee's project or reassign them to another user to complete.

[@BBI-Brandboost]

Thanks for sharing, it is nice and easy to follow which is a massive help.

[@thedevlife]

Great content. Gives motivation to keep our channel going.

[@agasthya3693]

Hey Kayle please do video on Gulp, Grunt, webpack and parcel & when to choose which tool

[@medAmineRg]

that was a great video thankyou so much!

[@RuiLopesFR]

Nice one - Just for the sake of DRY : scopedProjects = (user, projects) => projects.filter(project => canViewProject(user, project))

[@Sandeep-lb7wb]

could you please explain how to set admin role to the users who are registers first

[@rafishaaya1658]

great video though, would that be useful for a management systems as well?

[@danial9864]

Thank you so much for the tutorial video it's quite informative and professional

[@MrAlliqator]

Please make video how can create front side

[@larita182-x1k]

THANK YOUUUUUUUUUUU!!!!!! I finally understand this.

[@ayushthakur733]

So accurate with the name web dev SIMPLIFIED

[@Millonerium]

great video bro, please do a MERN project like this with frontend

[@-Nandakishore-wt5is]

Hi can you make a video for multiple type accounts using mern stack , for example there are two types of users regular users, product manufacturers, from which we will take different information from both of them. But we need to allow them to login from same page. Is it possible ?

[@josephlivengood4508]

You dont view anything in the browser? I'm using the ejs view engine and am having problems getting the ._id from mongodb to verify that the user is the owner of a post. I cannot find a work around. Maybe this would do it 🤔

[@mikexue5104]

it's 2021, so there is still NO out-of-box user /role management extension for Nodejs?

[@nirmesh44]

Perfect. Very nicely done

[@mallusrgreat]

Kyle to webcam: Focus on my hair not the content

[@awatanshpratapsingh120]

How to add the functionality in which admin can change the roles .

[@hindbensafi4646]

Thanks a lot ! great video ! Please how can i protect my front-end routes using those APIs ? For example, when users login, the Admin would have route to the admin page but normal users not ? is it secure to check roles in the front-end ?

[@ashiqsultanmohamed9765]

I recently deployed an express middle ware which exactly does this. Check route-access-control npm package

[@paularah8877]

will check it out, thanks!

[@alex_lomov]

Great layout of material.

[@billythemusical]

Hey! Thanks for the video, although I don't think the PROMO code works anymore 😩

[@bigbeeforever]

surely on signup you wouldnt have a choice of role, so how would you assign the ADMIN role other than everyone is BASIC. would this be done in the backend?

[@harshjindal5179]

hlo can u tell me how to compile and run this application ?

[@edisvelicanin8854]

exactly what i was looking for

[@chriisduran]

This lesson is great, just I would like add more basic users, the problem is that this example define the basic users from start What if i have a login that any users want to access? How define that all users logged with no id admin are basic? I´m stuck in that! :(

[@iurii7752]

The best educational videos

[@indigosay]

I added this video to my Gold Collection

[@pankaj_9998]

Thank you. This was a great learing experience.

[@alexandre3932]

Good tutorial, why sometimes did you use es6 and sometimes not ?

[@rishabsharma5307]

Awesome video

[@matiasmanevi1521]

How would you share the permissions logic between the node backend and a ... lets say, react frontend?

[@alikashif8098]

I am bit concerned with the performance of approach explained here, users are in some DB, say mongo or SQL, so are the roles and permissions, with this approach , on each call, I have to go to DB and verify that sent userId is valid(login basic Auth) and then proceed next middleware, and that middleware will again call the DB and look for role permissions on particular object (currently handelled with static data.js), thus with each request multiple calls to DB are being made. now consider an application with good amount of users intracing, Can you please shed some light on performance perspective?

[@BabasolaOso]

I love you and PedroTech, both kinda feel alike to me

[@amitshrestha898]

Found what I am looking for thanks.

[@zlatan1261]

After all, this method does not meet the requirements of security. The role is taken from the body. If I release basic instead of admin in the header, you will send the relevant information to the admin from the server. is that right?

[@bunnybloods768]

You are so great.can you tell me what is your main job besides youtube?

[@WebDevSimplified]

I am a fullstack web developer consultant.

[@swapnilkuwar7040]

What if we create capabilities for each action, and then assign that capability to the roles so that one capability can be assign to the multiple roles.

[@shabbirjodhpurwala6979]

I researched about this Adding body to get request is bad practise Isn't it?? Also if caching is used it would cause weird bugs..because caching mechanism usually ignore the get body Is this right?? What is the correct way to go about it??