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

Better entitlement framework in V3 #10253

Open
manasag opened this issue May 21, 2024 · 1 comment
Open

Better entitlement framework in V3 #10253

manasag opened this issue May 21, 2024 · 1 comment
Assignees
Labels
a/authz Issues related to "authorization" and the policy engine after session claims are procesed c/v3-engine V3 Metadata and Engine v3

Comments

@manasag
Copy link
Contributor

manasag commented May 21, 2024

Currently, Hasura uses role based access control, where you define the entire set of permissions per-role. However, this doesn't scale well because:

It's not always possible to capture all possible states in the authorization system as separate roles.
It's not possible to reuse permissions (allowed fields, model predicate) across roles.
For complicated permissions, it's hard to verify the correctness of a model's permissions predicate at a glance.

RFC on the proposal can be followed here #10237

V2 Issues that can be addressed by this proposal:

@manasag manasag added this to V3 May 21, 2024
@manasag manasag converted this from a draft issue May 21, 2024
@manasag manasag added a/authz Issues related to "authorization" and the policy engine after session claims are procesed c/v3-engine V3 Metadata and Engine labels May 21, 2024
@manasag manasag moved this from In progress to Backlog in V3 May 21, 2024
@manasag manasag added the v3 label May 22, 2024
@rahulagarwal13
Copy link
Contributor

rahulagarwal13 commented Jun 27, 2024

Related GH Issue - #10310

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/authz Issues related to "authorization" and the policy engine after session claims are procesed c/v3-engine V3 Metadata and Engine v3
Projects
Status: Backlog
Development

No branches or pull requests

3 participants