feat(group): add group permissions (#10853)

# Which Problems Are Solved
Ensuring the user group resource is managed with appropriate
permissions.

# How the Problems Are Solved
By configuring and checking for the relevant permissions needed to
create, read, update, and delete the user groups resource.

# Additional Changes
N/A

# Additional Context
- Related to #9702 
- Follow-up for PRs #10455,  #10758
This commit is contained in:
Gayathri Vijayan
2025-10-21 11:18:21 +02:00
committed by GitHub
parent ff869482b1
commit ebc6c503a3
13 changed files with 1065 additions and 145 deletions
+29
View File
@@ -1379,6 +1379,10 @@ InternalAuthZ:
- "userschema.read"
- "userschema.write"
- "userschema.delete"
- "group.create"
- "group.write"
- "group.read"
- "group.delete"
- Role: "IAM_OWNER_VIEWER"
Permissions:
- "iam.read"
@@ -1415,6 +1419,7 @@ InternalAuthZ:
- "action.execution.read"
- "userschema.read"
- "session.read"
- "group.read"
- Role: "IAM_ORG_MANAGER"
Permissions:
- "org.read"
@@ -1474,6 +1479,10 @@ InternalAuthZ:
- "project.grant.member.delete"
- "session.read"
- "session.delete"
- "group.create"
- "group.write"
- "group.read"
- "group.delete"
- Role: "IAM_USER_MANAGER"
Permissions:
- "org.read"
@@ -1502,6 +1511,7 @@ InternalAuthZ:
- "project.grant.member.read"
- "session.read"
- "session.delete"
- "group.read"
- Role: "IAM_ADMIN_IMPERSONATOR"
Permissions:
- "admin.impersonation"
@@ -1566,6 +1576,10 @@ InternalAuthZ:
- "project.grant.member.delete"
- "session.read"
- "session.delete"
- "group.create"
- "group.write"
- "group.read"
- "group.delete"
- Role: "IAM_LOGIN_CLIENT"
Permissions:
- "iam.read"
@@ -1604,6 +1618,7 @@ InternalAuthZ:
- "session.link"
- "session.delete"
- "userschema.read"
- "group.read"
- Role: "ORG_USER_MANAGER"
Permissions:
- "org.read"
@@ -1623,6 +1638,7 @@ InternalAuthZ:
- "project.role.read"
- "session.read"
- "session.delete"
- "group.read"
- Role: "ORG_OWNER_VIEWER"
Permissions:
- "org.read"
@@ -1644,6 +1660,7 @@ InternalAuthZ:
- "project.grant.read"
- "project.grant.member.read"
- "project.grant.user.grant.read"
- "group.read"
- Role: "ORG_SETTINGS_MANAGER"
Permissions:
- "org.read"
@@ -1674,6 +1691,7 @@ InternalAuthZ:
- "project.app.read"
- "project.grant.read"
- "project.grant.member.read"
- "group.read"
- Role: "ORG_PROJECT_PERMISSION_EDITOR"
Permissions:
- "org.read"
@@ -1939,6 +1957,10 @@ SystemAuthZ:
- "userschema.read"
- "userschema.write"
- "userschema.delete"
- "group.create"
- "group.write"
- "group.read"
- "group.delete"
- Role: "IAM_OWNER_VIEWER"
Permissions:
- "iam.read"
@@ -1975,6 +1997,7 @@ SystemAuthZ:
- "action.execution.read"
- "userschema.read"
- "session.read"
- "group.read"
- Role: "IAM_ORG_MANAGER"
Permissions:
- "org.read"
@@ -2034,6 +2057,10 @@ SystemAuthZ:
- "project.grant.member.delete"
- "session.read"
- "session.delete"
- "group.create"
- "group.write"
- "group.read"
- "group.delete"
- Role: "IAM_USER_MANAGER"
Permissions:
- "org.read"
@@ -2062,6 +2089,7 @@ SystemAuthZ:
- "project.grant.member.read"
- "session.read"
- "session.delete"
- "group.read"
- Role: "IAM_ADMIN_IMPERSONATOR"
Permissions:
- "admin.impersonation"
@@ -2107,6 +2135,7 @@ SystemAuthZ:
- "session.link"
- "session.delete"
- "userschema.read"
- "group.read"
# If a new projection is introduced it will be prefilled during the setup process (if enabled)
# This can prevent serving outdated data after a version upgrade, but might require a longer setup / upgrade process: