You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
By default, a principal that has a catalog_admin role in a catalog cannot list principal roles using the API. The catalog_admin's responsibility is managing privileges and access to the catalog roles in a catalog. After fixing #359 , the catalog_admin has the ability to grant a catalog role to a principal role, but has no ability to see the list of available principal roles. This may be ok for cases where a principal has both the service_admin and the catalog_admin roles, but if there's an enforced separation, the lack of privilege to list principal roles is a hindrance.
Describe the solution you'd like
The authorization model typically requires a catalog to be in the scope of a request in order to detect that user has catalog_admin on the specified catalog. However, PrincipalRoles are not tied to a catalog, so it's difficult for the current authorization workflow to know if the current user does have admin privilege on any catalog. We can consider a separate API, where the /principal_roles endpoint is prefixed by catalog, but that feels cumbersome - especially if the caller is an admin on multiple catalogs.
A more likely solution would be to manage a special PrincipalRole that has limited privileges on PrincipalRoles (and possibly Principals) that a user is automatically added to when granted catalog_admin.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
collado-mike
changed the title
[FEATURE REQUEST] CatalogAdmin cannot list principal roles
[FEATURE REQUEST] CatalogAdmin should be able to list principal roles
Oct 9, 2024
Is your feature request related to a problem? Please describe.
By default, a principal that has a
catalog_admin
role in a catalog cannot list principal roles using the API. Thecatalog_admin
's responsibility is managing privileges and access to the catalog roles in a catalog. After fixing #359 , thecatalog_admin
has the ability to grant a catalog role to a principal role, but has no ability to see the list of available principal roles. This may be ok for cases where a principal has both theservice_admin
and thecatalog_admin
roles, but if there's an enforced separation, the lack of privilege to list principal roles is a hindrance.Describe the solution you'd like
The authorization model typically requires a catalog to be in the scope of a request in order to detect that user has
catalog_admin
on the specified catalog. However, PrincipalRoles are not tied to a catalog, so it's difficult for the current authorization workflow to know if the current user does have admin privilege on any catalog. We can consider a separate API, where the/principal_roles
endpoint is prefixed by catalog, but that feels cumbersome - especially if the caller is an admin on multiple catalogs.A more likely solution would be to manage a special PrincipalRole that has limited privileges on PrincipalRoles (and possibly Principals) that a user is automatically added to when granted
catalog_admin
.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: