Jon,
On 6/13/22 15:28, jonmcalexan...@wellsfargo.com.INVALID wrote:
I'm sorry I interfered.
Sorry, I don't think my tone transmitted well via email.
I was mostly trying to be playful.
If you'd like to comment on making monitoring data available via Tomcat
using either the Manager app - or some other way - we'd be happy to have
your feedback.
Thanks,
-chris
-----Original Message-----
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: Monday, June 13, 2022 1:36 PM
To: dev@tomcat.apache.org
Subject: Re: Any interest in a read-only JMX role?
Jon,
On 6/13/22 13:43, jonmcalexan...@wellsfargo.com.INVALID wrote:
That's great if you use the manager app, but we don't use it or even make it
available.
Well... this /is/ a conversation about the JMXProxyServlet which is a part of
the Manager app. So either you have something to say (about
JMXProxyServlet) or you don't care about the whole discussion, right?
:)
-chris
-----Original Message-----
From: Konstantin Kolinko <knst.koli...@gmail.com>
Sent: Monday, June 13, 2022 11:54 AM
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Any interest in a read-only JMX role?
пн, 13 июн. 2022 г. в 19:32, Christopher Schultz
<ch...@christopherschultz.net>:
All,
I've been thinking about the possibility of making a read-only JMX
role available for the existing manager-jmx capability.
[...]
Does anyone think this is a good idea?
I think it is a bad idea, because passwords (and maybe other secrets)
are visible through JMX, by design.
It might be worth to have some "status" role, but it has to be
defined more specifically than just a "view all" role.
Maybe the way to achieve the same result is to amend the server
status page, which is already provided by the manager app and has a
dedicated role.
Best regards,
Konstantin Kolinko.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For
additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For
additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional
commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
