-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
有没有兴趣支持Graphql跟ABAC权限模型 #184
Comments
There are times when characters aren't good choices. Meanwhile second thought: |
There are times when characters aren't good choices. Meanwhile second thoughts: |
hi 我们这个设计的就是面向角色的API权限控制,目前没有规划支持ABAC
我觉得这个应该是业务去自己实现比较好,框架不能通用实现它 |
hi Our design is role-oriented API permission control, currently there is no plan to support ABAC
I think it is better for the business to implement it by itself, and the framework cannot implement it universally. |
有一些时候 角色并不是很好的选择。
如:我想针对每个前端按钮进行权限控制。
针对某一个用户做权限控制,而不影响到其他相同的权限。
同时第二个想法:
是否可以侵入到响应模型字段,比如admin角色下展示用户的明文密码,审计员则不展示用户的密码,用户自己展示自己的加密密码。
The text was updated successfully, but these errors were encountered: