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

Posted to issues@karaf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2017/12/07 07:21:00 UTC

[jira] [Moved] (KARAF-5527) the karaf.secured.command.compulsory.roles should only affect command ACL rules

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

Freeman Fang moved CXF-7582 to KARAF-5527:
------------------------------------------

    Estimated Complexity:   (was: Unknown)
                Workflow: classic default workflow  (was: Default workflow, editable Closed status)
                     Key: KARAF-5527  (was: CXF-7582)
                 Project: Karaf  (was: CXF)

> the karaf.secured.command.compulsory.roles should only affect command ACL rules
> -------------------------------------------------------------------------------
>
>                 Key: KARAF-5527
>                 URL: https://issues.apache.org/jira/browse/KARAF-5527
>             Project: Karaf
>          Issue Type: Bug
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> for the JMX ACL rules, it's hierarchical and hence we can simply add
> *=admin
> to the root jmx.acl.cfg to enforce all mbean operations without more specific match to be admin role.
> Currently enable karaf.secured.command.compulsory.roles also take effect for the JMX ACL rules which prevent the upper hierarchy rules take effect



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