This is an automated email from the ASF dual-hosted git repository.

csutherl pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/master by this push:
     new 9a3cc79  Clarify SSL Configuration attributes in 
JmxRemoteLifecycleListener documentation
9a3cc79 is described below

commit 9a3cc792463569487d288386472a66c95057be8c
Author: Coty Sutherland <csuth...@apache.org>
AuthorDate: Thu Apr 18 15:18:43 2019 -0400

    Clarify SSL Configuration attributes in JmxRemoteLifecycleListener 
documentation
---
 webapps/docs/config/listeners.xml | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/webapps/docs/config/listeners.xml 
b/webapps/docs/config/listeners.xml
index e488f82..983793b 100644
--- a/webapps/docs/config/listeners.xml
+++ b/webapps/docs/config/listeners.xml
@@ -511,15 +511,6 @@
     visualvm or a similar tool to a remote Tomcat instance that is running
     behind a firewall.</p>
 
-    <p>Note: The SSL configuration can be done with attributes identical to 
those
-    of <a href="http.html#SSL_Support_-_SSLHostConfig">SSLHostConfig</a> and 
the
-    properties of the default certificate as defined for
-    <a href="http.html#SSL_Support_-_Certificate">SSLHostConfigCertificate</a>.
-    This will create a JSSE SSLContext which will be given to the JMX/RMI 
registry
-    when creating the server socket. OpenSSL specific attributes cannot
-    be used in the configuration as JMX remote can only use a regular
-    SSLContext.</p>
-
     <p>The remainder of the configuration can be done via the standard system
     properties for configuring JMX. For further information on configuring JMX
     see
@@ -531,7 +522,8 @@
     element.</p>
 
     <p>The following additional attributes are supported by the <strong>JMX 
Remote
-    Lifecycle Listener</strong>, in addition to the SSL related attributes:</p>
+    Lifecycle Listener</strong>, in addition to the SSL related attributes 
noted below
+    in the "SSL Configurations" section:</p>
 
     <attributes>
 
@@ -619,7 +611,16 @@
     <code>letmein</code>.
     </p>
 
-    <h3>SSL configurations</h3>
+    <h3>SSL Configurations</h3>
+
+    <p>Note: SSL configuration can be done with attributes identical to those
+    of <a href="http.html#SSL_Support_-_SSLHostConfig">SSLHostConfig</a> and 
the
+    properties of the default certificate as defined for
+    <a href="http.html#SSL_Support_-_Certificate">SSLHostConfigCertificate</a>.
+    This will create a JSSE SSLContext which will be given to the JMX/RMI 
registry
+    when creating the server socket. OpenSSL specific attributes <strong>cannot
+    </strong> be used in the configuration as JMX remote can only use a regular
+    SSLContext.</p>
 
     <p>A certificate can be defined for the server using a keystore:</p>
   <source><![CDATA[  <Listener 
className="org.apache.catalina.mbeans.JmxRemoteLifecycleListener"


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to