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 2014/10/17 09:43:33 UTC

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

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

Freeman Fang updated KARAF-3293:
--------------------------------
    Fix Version/s: 2.4.1
                   3.0.3
                   4.0.0

> 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
>             Fix For: 4.0.0, 3.0.3, 2.4.1
>
>
> 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)