René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Dynamic Role Model partly allows users to create users with more rights","articleBody":"\u003c!--\r\nVerify first that your issue/request is not already reported on GitHub.\r\nAlso test if the latest release and main branch are affected too.\r\nAlways add information AFTER of these HTML comments, but no need to delete the comments.\r\n--\u003e\r\n\r\n##### ISSUE TYPE\r\n\u003c!-- Pick one below and delete the rest --\u003e\r\n * Bug Report\r\n\r\n\r\n##### COMPONENT NAME\r\n\u003c!--\r\nCategorize the issue, e.g. API, VR, VPN, UI, etc.\r\n--\u003e\r\n~~~\r\nAPI\r\n~~~\r\n\r\n##### CLOUDSTACK VERSION\r\n\u003c!--\r\nNew line separated list of affected versions, commit ID for issues on main branch.\r\n--\u003e\r\n\r\n~~~\r\n4.16.0\r\n~~~\r\n\r\n##### CONFIGURATION\r\n\u003c!--\r\nInformation about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise\r\n--\u003e\r\nN/A\r\n\r\n##### OS / ENVIRONMENT\r\n\u003c!--\r\nInformation about the environment if relevant, N/A otherwise\r\n--\u003e\r\nN/A\r\n\r\n##### SUMMARY\r\n\u003c!-- Explain the problem/feature briefly --\u003e\r\nA new role, for example \"Domain Admin Restricted\", is created by a Root Admin Account based on existing role \"Domain Admin\"\r\nSome functionality is restricted of the role \"Domain Admin Restricted\" with setting \"Deny\" for some APIs, for example createServiceOffering.\r\nA new Account/User, DAJonDoeRestricted, is created based on the role \"Domain Admin Restricted\".\r\nThe user \"DAJonDoeRestricted\" is not allowed to execute createServiceOffering.\r\nBut the user DAJonDoeRestricted is allowed to create a new Account based on the default role \"Domain Admin\".\r\nFor this user, the deny rules of role Domain Admin Restricted are not inherited and do not apply.\r\nThe newly created user has higher rights than the restricted user.\r\n\r\n##### STEPS TO REPRODUCE\r\n\u003c!--\r\nFor bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.\r\n\r\nFor new features, show how the feature would be used.\r\n--\u003e\r\nCreate Role \"Domain Admin Restricted\" based on \"Domain Admin\"\r\nRestrict functionality by choosing Deny for \"createServiceOffering\"\r\nCreate an Account \"DAJonDoeRestricted\" based on \"Domain Admin Restricted\"\r\nLogin as account \"DAJonDoeRestricted\"\r\nCreate a new account \"DAJaneDoeNotrestricted\" based on Role \"Domain Admin\"\r\nLogout user \"DAJonDoeRestricted\"\r\nLogin user \"DAJaneDoeNotrestricted\"\r\n\r\nUser \"DAJonDoeRestricted\" is not allowed to issue createServiceOffering.\r\nUser \"DAJaneDoeNotrestricted\" is allowed to issue createServiceOffering.\r\n\r\n\u003c!-- Paste example playbooks or commands between quotes below --\u003e\r\n\r\n\r\n\u003c!-- You can also paste gist.github.com links for larger files --\u003e\r\n\r\n##### EXPECTED RESULTS\r\n\u003c!-- What did you expect to happen when running the steps above? --\u003e\r\n\r\n\r\nAccounts should not be able to create accounts with rights for more functionality than they are allowed themselves.\r\nRestrictions should be inherited or the ability to create accounts based on Roles with more functionality rights should not be given.\r\n\r\n\r\n##### ACTUAL RESULTS\r\n\u003c!-- What actually happened? --\u003e\r\n\r\n\u003c!-- Paste verbatim command output between quotes below --\u003e\r\n\r\nAccounts based restricted roles, which were based on Domain Admin role, are able to create Accounts with original/unrestricted Domain Admin functionality rights.\r\n\r\n","author":{"url":"https://github.com/StepBee","@type":"Person","name":"StepBee"},"datePublished":"2021-12-15T17:56:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/5781/cloudstack/issues/5781"}