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/06/06 05:56:02 UTC

[jira] [Created] (KARAF-3024) RBAC - Support wildcard in jmx.acl.....cfg filename

Freeman Fang created KARAF-3024:
-----------------------------------

             Summary: 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
            Reporter: Freeman Fang


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)