知识卡片
共享计算按请求收窄权限
共享服务处理多个租户,请求到来后根据其上下文取得当前租户的受限凭证,再用于下游访问。若业务代码还能取得原始宽权限,就存在绕过路径;因此应让受限上下文注入标准执行链,并减少开发者自行选择权限的机会。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Tenant Isolation · 查看原书依据
on the code and libraries of my solution. This does leave room for microservices to make choices that go around your isolation mechanisms. However, the more work you put into injecting this isolation context into your code outside the view of developers, the better chances you have of enforcing compliance with your overall isolation strategy.
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第09章《Tenant Isolation》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch09.html)
- 结论依据:原文具体说明共享服务处理多个租户,请求到来后根据其上下文取得当前租户的受限凭证,再用于下游访问;本卡据此归纳机制及适用边界。
- 原始内容:on the code and libraries of my solution. This does leave room for microservices to make choices that go around your isolation mechanisms. However, the more work you put into injecting this isolation context into your code outside the view of developers, the better chances you have of enforcing compliance with your overall isolation strategy.