[jira] [Resolved] (KARAF-3293) more fine-grained way to specify the jmx.acl.whitelist.cfg

["Freeman Fang (JIRA)" <ji...@apache.org>]

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

Freeman Fang resolved KARAF-3293.
---------------------------------
    Resolution: Fixed

commit fix
http://git-wip-us.apache.org/repos/asf/karaf/commit/edb7b1bc for karaf-2.x branch
http://git-wip-us.apache.org/repos/asf/karaf/commit/92047740 for karaf-3.0.x branch
http://git-wip-us.apache.org/repos/asf/karaf/commit/7623268d for master

> more fine-grained way to specify the jmx.acl.whitelist.cfg 
> -----------------------------------------------------------
>
>                 Key: KARAF-3293
>                 URL: https://issues.apache.org/jira/browse/KARAF-3293
>             Project: Karaf
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> currently in jmx.acl.whitelist.cfg  we can specify an ObjectName to bypass the RBAC check, this way all operations and attributes are accesiable under a cerntain ObjectName, however, in some cases we only wanna bypass RBAC check for some operations|atttributes under a certain ObjectName, so we should extend the logic in  jmx.acl.whitelist.cfg a bit to provide a more fine-grained way.
> some thing like
> objectname;operationName=bypass



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)