[
https://issues.apache.org/jira/browse/CLOUDSTACK-10044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123146#comment-16123146
]
ASF subversion and git services commented on CLOUDSTACK-10044:
--------------------------------------------------------------
Commit 3f330a219916083fa6c91ee7b83ee6caaa70b9c1 in cloudstack's branch
refs/heads/master from [~nicolas.vazquez]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3f330a2 ]
CLOUDSTACK-10044: Update role permission (#2236)
This feature allows changing permission for existing role permissions, as those
were static and could not be changed once created. It also provides the ability
to change these permissions in the UI using a drop down menu for each
permission rule, in which admin can select ‘Allow’ or ‘Deny’ permission.
Changes in the API:
This feature modifies behaviour of updateRolePermission API method:
New optional parameters ‘ruleid’ and ‘permission’ are introduced, they are
mutual exclusive to ‘ruleorder’ parameter. This defines two use cases:
Update role permission: ‘ruleid’ and ‘permission’ parameters needed
Update rules order: ‘ruleorder’ parameter needed
Parameter ‘ruleorder’ is now optional
updateRolePermission providing ‘ruleorder’ parameter should be sent via POST
> Update rule permission of a role permission
> -------------------------------------------
>
> Key: CLOUDSTACK-10044
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10044
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.11.0.0
> Reporter: Nicolas Vazquez
> Assignee: Nicolas Vazquez
> Fix For: 4.11.0.0
>
> Attachments: UpdateRolePermissionUI.jpg
>
>
> h3. Introduction
> This feature allows to change permission for existing role permissions, as
> those were static and could not be changed once created. It also provides the
> ability to change these permissions in the UI using a drop down menu for each
> permission rule, in which admin can select ‘Allow’ or ‘Deny’ permission.
> h3. Changes in the API:
> This feature modifies behaviour of {{updateRolePermission}} API method:
> * New optional parameters ‘ruleid’ and ‘permission’ are introduced, they are
> mutual exclusive to ‘ruleorder’ parameter. This defines two use cases:
> ** Update role permission: ‘ruleid’ and ‘permission’ parameters needed
> ** Update rules order: ‘ruleorder’ parameter needed
> * Parameter ‘ruleorder’ is now optional
> * updateRolePermission providing ‘ruleorder’ parameter should be sent via POST
> h3. Changes in the UI:
> Drop down menu added for role rule-permissions as seen in attached picture
> !UpdateRolePermissionUI.jpg|UI!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
