Skip to content

Global setting to disallow domain admin to change domain and account settings #7296

Open

Description

@soreana
ISSUE TYPE
  • Bug Report
COMPONENT NAME
UI, Permissions, Access Controll
CLOUDSTACK VERSION
4.17 onwards
SUMMARY

The #4339 pull request allows CloudStack's domain admins to change their domains configurations. This option gives domain admins power to abuse CloudStack system IPs, create public templates, share their templates with other domains, and many more unwanted effects to the environments even though the root admin disallow these actions in the first place.

Domain level settings
account.allow.expose.host.hostname
allow.public.user.templates
preferred.storage.pool
share.public.templates.with.other.domains
use.system.public.ips

As of now there isn't a global setting to revert this changes. I have the following suggestions let me know what do you think.

  1. Add a global setting to override this behaviour.
  2. Move these setting to global level so domain admins can't change them.
  3. Give priority to the global level settings, so if domain admins override a setting.
STEPS TO REPRODUCE
1. Login as a root admin
2. Configure the domain
3. Log out
4. Login as a domain admin
5. Configure the domain
EXPECTED RESULTS
Root admin configurations are **NOT** overridden.
ACTUAL RESULTS
Root admin configurations are overridden.

Activity

  1. DaanHoogland commented on Feb 28, 2023

    @DaanHoogland
    Contributor

    @soreana these all done by updateConfiguration. I think this calls for a more fine grained access control system for settings. I do not think either of you proposals are going to satisfy all use-cases.
    just €0,02

  2. soreana commented on Feb 28, 2023

    @soreana
    MemberAuthor

    @soreana these all done by updateConfiguration. I think this calls for a more fine grained access control system for settings. I do not think either of you proposals are going to satisfy all use-cases.
    just €0,02

    @DaanHoogland I'm totally agree with your proposal. Your proposed feature could be implemented in 4.19. What I proposed could be a small feature in 4.18.1.

  3. added this to the 4.19.0.0 milestone on Jun 22, 2023
  4. modified the milestones: 4.19.0.0, 4.20.0.0 on Dec 14, 2023
  5. modified the milestones: 4.20.0.0, unplanned on Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions