Skip to content

Conversation

@kofzera
Copy link
Contributor

@kofzera kofzera commented Sep 18, 2023

  • Allowed RESOURCEADMIN, TRUSTEDFACILITYADMIN and RESOURCEOBSERVER to
    read GROUPADMIN and GROUPMEMBERSHIPMANAGER in the VO.
  • This way the resource managers know who to contact in the matter
    of membership in the assigned groups.

Copy link
Contributor

@xflord xflord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should work, just make sure to manually test as well (some other policies might be used in the gui app).
Would be nice to include why this change was made in the commit message.

I just thought of a scenario where some group in the VO could be managed solely by VOADMINs, in which case the RESOURCEADMIN still does not know who to contact. Not sure how often this happens in production though. Also, this was not defined in the task, it's more just a question for @balcirakpeter

- Allowed RESOURCEADMIN, TRUSTEDFACILITYADMIN and RESOURCEOBSERVER to
read GROUPADMIN and GROUPMEMBERSHIPMANAGER in the VO.
- This way the resource managers know who to contact in the matter
of membership in the assigned groups.
@kofzera kofzera force-pushed the allow_resource_manager_read_subgroup_managers branch from 9b8f3e2 to ba1bb15 Compare September 18, 2023 11:13
@xflord xflord merged commit 786fa4e into CESNET:master Sep 21, 2023
@github-actions
Copy link

🎉 This PR is included in version 30.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants