https://issues.apache.org/bugzilla/show_bug.cgi?id=53139
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
As I stated before, JMX is an administration interface and as such has access
to all sorts of internal details. This particular internal detail is of use
when remotely administering instances via JMX.
Unfortunately, JMX does not support fine-grained access controls. You are
limited to users having read access or read/write access to everything (as an
aside, fine grained JMX access control could be an interesting project).
The Tomcat code is not going to be changed to remove this attribute. The
work-around you have adopted seems perfectly reasonable to me.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
