You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Pan, Julian (JIRA)" <ji...@apache.org> on 2017/12/08 05:41:00 UTC

[jira] [Resolved] (KYLIN-2938) Project Update ACL issue

     [ https://issues.apache.org/jira/browse/KYLIN-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pan, Julian resolved KYLIN-2938.
--------------------------------
    Resolution: Fixed

Already change to @PreAuthorize(Constant.ACCESS_HAS_ROLE_ADMIN + " or hasPermission(#currentProject, 'ADMINISTRATION')") in master branch

> Project Update ACL issue
> ------------------------
>
>                 Key: KYLIN-2938
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2938
>             Project: Kylin
>          Issue Type: Bug
>          Components: REST Service
>    Affects Versions: v2.1.0
>            Reporter: Pan, Julian
>            Assignee: Pan, Julian
>
> I noticed there different security between updateProject and renameProject in ProjectService.
> @PreAuthorize(Constant.ACCESS_HAS_ROLE_ADMIN + " or hasPermission(#currentProject, 'ADMINISTRATION') or hasPermission(#currentProject, 'MANAGEMENT')")
> updateProject
>  @PreAuthorize(Constant.ACCESS_HAS_ROLE_ADMIN + " or hasPermission(#currentProject, 'ADMINISTRATION')")
> renameProject
> Even updateProject will call renameProject. Which will throws exception if user is MANAGEMENT role.
> The renameProject should be same security check with updateProject.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)