[
https://issues.apache.org/jira/browse/CLOUDSTACK-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav resolved CLOUDSTACK-639.
------------------------------------
Resolution: Fixed
Fix in commits in above commits. Created Part-2 as a subtask.
> API Refactoring: Adapters for ACL
> ---------------------------------
>
> Key: CLOUDSTACK-639
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-639
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
>
> The work is to do the access control checks and entities checks using
> adapters.
> Part 1: APIAccessChecker to check if caller can evoke given API command.
> Implement a static role based checker using commands.properties file to check
> necessary roles for the command (the old school way CS used to do it)
> Part 2: Entity access checkers to check is caller can do operations on an
> entity. May use existing DomainChecker implementation. We may need to group
> entities in two groups (Infra entity like datacenter, disk offering etc. and
> controlled entity like those which have domain and accountid)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
