知识卡片
关系授权表达资源归属
关系授权ReBAC把用户与资源的关系纳入决定,例如某人是某项目成员或某文档拥有者,补足纯固定角色不易表达的逐对象规则。书中以Zanzibar及相关实现为参照,没有给出完整模型。是否采用应由实际关系查询需求决定,复杂度和产品支持也要核验,不能因名字新就替代简单RBAC。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构中的安全 · 查看原书依据
RBAC also has its limitations. For example, there is no simple way to tell if the owner of each item can edit or delete the item (such as a book in the bookstore). An extended form of RBAC, which supports advanced queries, is called Relationship-based access control (ReBAC).2 Google’s Zanzibar is a comprehensive authorization model built using these ideas, and you can find an open-source implementation of it at https://github.com/ory/keto.
参考来源
- 位置:《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)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:RBAC also has its limitations. For example, there is no simple way to tell if the owner of each item can edit or delete the item (such as a book in the bookstore). An extended form of RBAC, which supports advanced queries, is called Relationship-based access control (ReBAC).2 Google’s Zanzibar is a comprehensive authorization model built using these ideas, and you can find an open-source implementation of it at https://github.com/ory/keto.