知识卡片
认证成功不等于租户隔离
认证说明用户通过身份校验,并可产生带租户上下文的令牌,但业务代码仍可能访问其他租户资源。隔离需另外施加边界约束,把上下文落实为访问权限;即使每个请求都携带租户ID,也不能据此宣称已阻止越权。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Onboarding and Identity · 查看原书依据
authenticated user—can access the resources of another tenant. Tenant isolation builds upon the tenant context that you get from an authenticated user, implementing a completely separate layer of controls and measures to ensure that your code is not allowed to cross a tenant boundary. You’ll get a deeper look at these strategies in Chapter 9.
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第04章《Onboarding and Identity》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch04.html)
- 结论依据:原文具体说明认证说明用户通过身份校验,并可产生带租户上下文的令牌,但业务代码仍可能访问其他租户资源;本卡据此归纳机制及适用边界。
- 原始内容:authenticated user—can access the resources of another tenant. Tenant isolation builds upon the tenant context that you get from an authenticated user, implementing a completely separate layer of controls and measures to ensure that your code is not allowed to cross a tenant boundary. You’ll get a deeper look at these strategies in Chapter 9.