Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 13 Jun 2012 01:47:42 +0000 (UTC)
From: "Forrest Xia (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: <677399168.10288.1339552062607.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <697909430.36728.1333086898995.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (GERONIMO-6314) Add monitor role  to protect the
 JMX access
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Forrest Xia resolved GERONIMO-6314.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.0-beta-2)
                   3.0
    
> Add monitor role  to protect the JMX access 
> --------------------------------------------
>
>                 Key: GERONIMO-6314
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6314
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: connector, JVM-compatibility
>    Affects Versions: 3.0-beta-1
>         Environment: linux,windows
>            Reporter: Tina Li
>            Assignee: Tina Li
>             Fix For: 3.0
>
>         Attachments: GERONIMO-6314_formatUpdated.patch
>
>
> Currently, only the admin user can connect to JMX and the admin user has read/write access to MBeans. Now find a method to let "monitor" role also can access JMX but only has read-only access. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira