[ 
https://issues.apache.org/jira/browse/KARAF-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281432#comment-16281432
 ] 

ASF subversion and git services commented on KARAF-5527:
--------------------------------------------------------

Commit 23e0d52ba63e9a55c21b52709cfe253bbfbcf958 in karaf's branch 
refs/heads/karaf-4.1.x from [~ffang]
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=23e0d52 ]

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

(cherry picked from commit 2140673c9d5c0d73d3cf2da4fb6918f6acc681f5)


> 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)

Reply via email to