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
{{ message }}
Repository navigation
listSystemVmsUsageHistory is available to Domain Admin by Default #10031
We found that out of the box listSystemVmsUsageHistory is available to the Domain Admin Role with Type set to DomainAdmin by default. This feels like a bug since no other SystemVM API's are available. We worked around this issue by denying the API, however, I wanted to report it.
STEPS TO REPRODUCE
Create an account/user with the Domain Admin Role and set the Type to DomainAdmin. Run listSystemVmsUsageHistory
changed the title [-]listSystemVmsUsageHistory is available to DomainAdmin by Default[/-][+]listSystemVmsUsageHistory is available to Domain Admin by Default[/+]on Dec 3, 2024
It's not hurtful, but it took us some time to figure out what the problem was. We created a Root Admin role that denied access to *SystemVM* (We needed them to be able to create Domain Admin Accounts & Networks w/VLANS). After doing some comparing of ListAPI this was the one that stood out.
Is there a valid reason a Doman Admin should be able to use listSystemVmsUsageHistory? It seems odd since a Domain Admin can't even run ListSystemVMs
It's not hurtful, but it took us some time to figure out what the problem was. We created a Root Admin role that denied access to *SystemVM* (We needed them to be able to create Domain Admin Accounts & Networks w/VLANS). After doing some comparing of ListAPI this was the one that stood out.
Is there a valid reason a Doman Admin should be able to use listSystemVmsUsageHistory? It seems odd since a Domain Admin can't even run ListSystemVMs
I do not know of a reason. It might have been a slip of the keyboard, or someone wanted domain admins to be able to see the costs burned in their domain. I can imagine usage being of interest to a domain admin. So, yes, there might be a valid reason. I agree that it seems counter intuitive somewhat but not a bug. By the looks you found a valid way to deal with it.
I was asking because I wonder if we want this solved in code or "solved" in documentation.
Activity
[-]listSystemVmsUsageHistory is available to DomainAdmin by Default[/-][+]listSystemVmsUsageHistory is available to Domain Admin by Default[/+]DaanHoogland commentedon Dec 3, 2024
Do you really feel this is hurtful @scottsignal ?
scottsignal commentedon Dec 3, 2024
It's not hurtful, but it took us some time to figure out what the problem was. We created a Root Admin role that denied access to
*SystemVM*(We needed them to be able to create Domain Admin Accounts & Networks w/VLANS). After doing some comparing of ListAPI this was the one that stood out.Is there a valid reason a Doman Admin should be able to use
listSystemVmsUsageHistory? It seems odd since a Domain Admin can't even runListSystemVMsDaanHoogland commentedon Dec 4, 2024
I do not know of a reason. It might have been a slip of the keyboard, or someone wanted domain admins to be able to see the costs burned in their domain. I can imagine usage being of interest to a domain admin. So, yes, there might be a valid reason. I agree that it seems counter intuitive somewhat but not a bug. By the looks you found a valid way to deal with it.
I was asking because I wonder if we want this solved in code or "solved" in documentation.
api: fix access for listSystemVmUsageHistory
DaanHoogland commentedon Dec 5, 2024
@scottsignal , @shwstppr made a fix in #10032 . Can you test this?
DaanHoogland commentedon Jan 20, 2025
fixed in #10032