知识卡片
ACL与RBAC授权有别
ACL把允许主体和动作附着到具体对象,RBAC通过角色汇集权限再分配用户。前者适合对象粒度,后者便于组织治理;过细角色可能爆炸,过粗角色又会扩大权限,需要生命周期和审查而非只选一种模型。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Data Governance and Data Security · 查看原书依据
The main disadvantage of RBAC is the danger of “role explosion.” Within any large organization, there will be a large number of different roles, for people in different departments, subdepartments, and functions. Managing all of these roles can become a complex affair: if you don’t want to use a coarse-grained role model, you’ll likely end up with thousands of different roles. Another problem with RBAC
参考来源
- 位置:《Data Management at Scale》第08章《Data Governance and Data Security》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292,源文件:extracted/Data Management at Scale/_epub-src/OEBPS/ch08.html)
- 结论依据:原文对role explosion的解释、约束及上下文支持本卡;内容为中文归纳,不把架构建议当作所有组织的必然规律。
- 原始内容:The main disadvantage of RBAC is the danger of “role explosion.” Within any large organization, there will be a large number of different roles, for people in different departments, subdepartments, and functions. Managing all of these roles can become a complex affair: if you don’t want to use a coarse-grained role model, you’ll likely end up with thousands of different roles. Another problem with RBAC