[
https://issues.apache.org/jira/browse/CLOUDSTACK-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259477#comment-15259477
]
ASF GitHub Bot commented on CLOUDSTACK-8562:
--------------------------------------------
Github user jburwell commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-214960750
@mlsorensen +1 -- well said. command.properties presents a number of
significant problems. First, in a clustered environment, it is possible (and
quite easy) for there to be inconsistent security policies across the cluster.
Second, command.properties does not permit the definition of new roles.
Limiting users to 4 roles in a modern cloud environment is a barrier to
CloudStack adoption.
As Marcus has stated, we can't move forward if we keep trying to maintain
outdated mechanisms. Existing users can continue to use command.properties and
migrate if/when they desire. New users gain the benefits of a more reliable
and flexible authorization implementation.
> User Definable Roles
> --------------------
>
> Key: CLOUDSTACK-8562
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8562
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Paul Angus
> Assignee: Rohit Yadav
>
> Static command.properties moved to database and made user definable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
