Skip to content
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

Open
Jamel-jun opened this issue May 29, 2023 · 4 comments
Open

有没有兴趣支持Graphql跟ABAC权限模型 #184

Jamel-jun opened this issue May 29, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@Jamel-jun
Copy link

有一些时候 角色并不是很好的选择。
如:我想针对每个前端按钮进行权限控制。
针对某一个用户做权限控制,而不影响到其他相同的权限。

同时第二个想法:
是否可以侵入到响应模型字段,比如admin角色下展示用户的明文密码,审计员则不展示用户的密码,用户自己展示自己的加密密码。

@Jamel-jun Jamel-jun added the enhancement New feature or request label May 29, 2023
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


There are times when characters aren't good choices.
For example: I want to control permissions for each front-end button.
Do permission control for a certain user without affecting other same permissions.

Meanwhile second thought:
Whether it is possible to intrude into the response model field, for example, the user's plaintext password is displayed under the admin role, but the auditor does not display the user's password, and the user displays his own encrypted password.

@Jamel-jun
Copy link
Author

There are times when characters aren't good choices.
For example: I want to control permissions for each front-end button.
Do permission control for a certain user without affecting other same permissions.

Meanwhile second thoughts:
Whether it is possible to intrude into the response model field, for example, the user's plaintext password is displayed under the admin role, but the auditor does not display the user's password, and the user displays his own encrypted password.

@tomsun28
Copy link
Member

hi 我们这个设计的就是面向角色的API权限控制,目前没有规划支持ABAC

是否可以侵入到响应模型字段,比如admin角色下展示用户的明文密码,审计员则不展示用户的密码,用户自己展示自己的加密密码。

我觉得这个应该是业务去自己实现比较好,框架不能通用实现它

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


hi Our design is role-oriented API permission control, currently there is no plan to support ABAC

Whether it is possible to intrude into the response model field, for example, the user's plaintext password is displayed under the admin role, but the auditor does not display the user's password, and the user displays his own encrypted password.

I think it is better for the business to implement it by itself, and the framework cannot implement it universally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants