roryqi opened a new issue, #10412: URL: https://github.com/apache/gravitino/issues/10412
### Describe the subtask Problem Description Currently, Gravitino's authorization checks are performed primarily by directly matching the user's identity against permissions or role assignments. However, in a practical system with group support, a user's effective permissions should also derive from their group memberships​ in two key aspects: Group-based Ownership: A user may need to act as the "owner" of a resource not because they are the direct user:owner, but because they belong to a group:that is the resource's owner. The current logic does not evaluate this indirect ownership via group membership. Role Inheritance via Groups: A role (a collection of privileges) is often granted to a group, and all members of that group should inherit that role's permissions. The current authorization engine likely lacks this indirect evaluation path. This limitation makes the newly introduced group ownership and group-based role grants ineffective during permission checks, breaking core use cases for team-based management. Goal Extend the core authorization logic to evaluate a user's permissions by considering the groups they belong to, specifically for: Determining if a user effectively "owns" a resource (because their group owns it). Determining if a user has a specific privilege (because a role granting that privilege is assigned to one of their groups) ### Parent issue #10404 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
