知识卡片
ACL与RBAC分配粒度不同
访问控制列表ACL逐项保存用户对资源的操作权限,直观但人数增加后管理繁琐。RBAC把权限组成角色、用户组成组,再建立组与角色的映射,新增用户通常只需入组。它适合大多数组织权限管理,却难以仅凭固定角色表达“每项资源只有其拥有者能改”的动态关系。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构中的安全 · 查看原书依据
The most widely used authorization model is called a role-based access control (RBAC). This model includes users, groups, permissions, and roles. As Figure 8.3 shows, a group is a collection of users. Permissions are things users can do within the system, and roles are a collection of permissions. Authorizations are defined only as the mapping between groups and roles.
参考来源
- 位置:《Software Architecture and Decision-Making》第08章《宏观架构中的安全》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch08.xhtml)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:The most widely used authorization model is called a role-based access control (RBAC). This model includes users, groups, permissions, and roles. As Figure 8.3 shows, a group is a collection of users. Permissions are things users can do within the system, and roles are a collection of permissions. Authorizations are defined only as the mapping between groups and roles.