I liked your video halfway through watching it. Good work.
thanks for the explanation. It helps immensely.
Excellently laid out presentation! Very approachable and immediately helpful in unraveling my confusion about where exactly does RBAC fit into the overall access model :-)
Thank's bro! It has helped me a lot!
Fantastic video.
Great topic,
Could you do a video with 'real life' examples & how they would be implemented in a SQL database?
Thank you Sir
perfect
Thank you so much Mr. Erick for this seamless explanation on RBAC. My question is, is RBAC a software or a programme. what is it exactly? Thank you.
It's neither nor, @ezenwa. It's just a model of hoe to manage access to resources. It's implemented by many different software vendors,
These functions come in-corperated in different softwares. eg an accounting software
I'd assume that one role could be shared by multiple users. So that makes it a many-many relationship. Same applies to the next two relations.
right, @jayanth. and it's probably even a bit of an anti-pattern if a role is only assigned to one user. after all, separating roles and users is the main idea behind RBAC.
Is there a difference between capabilities and resources here? Because in capability lists, a capability denotes a pair of object and access right.
In the multi mapping between permissions and capabilities, it becomes blurry, because a permission could be atomic. The permission could also be viewed as for the individual resource/capability, in the example, one permission could govern one system, the other system could be a separate permission.
RBAC
ty burrel knows tech
Is any video about ABAC model ?
There's isn't an ABAC video at the moment, but it's a good idea! Essentially, ABAC is a generalization of RBAC where attributes can be used for controlling access that can represent anything (including roles).
Excellent .. Slide online link is broken. Could you please share the updated link or a copy? Thanks
Thanks for the feedback. The link isn't broken but my web server is old and doesn't support HTTPS. Today's web isn't all that supportive anymore of this old access method, but sadly that's all I have available for now.
looks like a many to many relation ship
user - role
role - permission
Exactly. This is what makes the model so powerful when you have many resources and many users. The role is the intermediary layer to model the relationships in a more scalable way.
Very helpful video, May God bless you with love, care and mercy.
Thank you very much, your comment made my day!