Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Fri, 6 Jun 2014 03:58:01 +0000 (UTC)
From: "Freeman Fang (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12718769.1402026960810.80031.1402027081707@arcas>
In-Reply-To: <JIRA.12718769.1402026960810@arcas>
References: <JIRA.12718769.1402026960810@arcas>
Subject: [jira] [Work started] (KARAF-3024) RBAC - Support wildcard in
 jmx.acl.....cfg filename
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Work on KARAF-3024 started by Freeman Fang.

> RBAC - Support wildcard in jmx.acl.....cfg filename
> ---------------------------------------------------
>
>                 Key: KARAF-3024
>                 URL: https://issues.apache.org/jira/browse/KARAF-3024
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-security
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.4.0, 4.0.0, 3.0.2
>
>
> the pattern of jmx.acl.....cfg comes from the jmx ObjectName, basically it's the domain name + property value(the order matters here). Some property value is dynamically created so that the ObjectName could change due to different MBean instance.
> For example,  an ObjectName looks like
> org.apache.activemq:type=Broker,brokerName=amq-broker,service=Health
> here the brokerName would change for different amq brokers, so it's better we can provide a way  so that one jmx.acl configuration file can match all brokers with service "Health", so the file name could be like
> {code}
> jmx.acl.org.apache.activemq.Broker._.Health.cfg
> {code}
> here the "_" is just a placeholder and can match all brokers


--
This message was sent by Atlassian JIRA
(v6.2#6252)