You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by ms...@apache.org on 2002/03/11 23:20:00 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual component_reference.xml get-started.xml
mstover1 02/03/11 14:20:00
Modified: docs running.html
docs/usermanual component_reference.html get-started.html
xdocs/usermanual component_reference.xml get-started.xml
Log:
Adding documentation about the SSL Manager
Revision Changes Path
1.37 +0 -0 jakarta-jmeter/docs/running.html
Index: running.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/running.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- running.html 9 Mar 2002 23:47:57 -0000 1.36
+++ running.html 11 Mar 2002 22:19:57 -0000 1.37
@@ -243,7 +243,7 @@
<br >
</br>
-$Id: running.html,v 1.36 2002/03/09 23:47:57 mstover1 Exp $
+$Id: running.html,v 1.37 2002/03/11 22:19:57 mstover1 Exp $
</font>
<br >
1.10 +76 -0 jakarta-jmeter/docs/usermanual/component_reference.html
Index: component_reference.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/component_reference.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- component_reference.html 7 Mar 2002 23:03:12 -0000 1.9
+++ component_reference.html 11 Mar 2002 22:19:58 -0000 1.10
@@ -120,6 +120,7 @@
<li><a href="#Miscellaneous_Features">13.7 Miscellaneous Features</a></li>
<ul>
<li><a href="#Data_Analyzer">Data Analyzer</a></li>
+ <li><a href="#SSL_Manager">SSL Manager</a></li>
</ul>
</ul>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
@@ -2514,6 +2515,81 @@
<p><b>Control Panel</b></p>
<div align="center"><img src="../images/screenshots/data_analyzer.gif"></div>
</td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <hr>
+ <table border="0" cellspacing="0" cellpadding="2">
+ <tr><td>
+ <font face="arial,helvetica,sanserif">
+ <a name="SSL_Manager"><h3>13.7.2 SSL Manager</h3></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <p >
+
+ The SSL Manager is a way to select a client certificate so that you can test
+ applications that use Public Key Infrastructure (PKI). In order to use it,
+ you must have JSSE 1.0.2 installed. Unfortunately, there is no standard method
+ for controling who a client is--and that won't be introduced until JDK 1.4 is
+ officially available. The SSL Manager should still work with JDK 1.4, so this
+ is the best solution we could come up with.
+
+ </p>
+ <b >
+ Choosing a Client Certificate
+ </b>
+ <p >
+
+ You may either use a Java Key Store (JKS) format key store, or a Public Key
+ Certificate Standard #12 (PKCS12) file for your client certificates. There
+ is a bug in the JSSE libraries that require you to have at least a six character
+ password on your key (at least for the keytool utility that comes with your
+ JDK).
+
+ </p>
+ <p >
+
+ To select the client certificate, choose Options->SSL Manager from the menu bar.
+ You will be presented with a file finder that looks for PKCS12 files by default.
+ Your PKCS12 file must have the extension '.p12' for SSL Manager to recognize it
+ as a PKCS12 file. Any other file will be treated like an average JKS key store.
+ If JSSE is correctly installed, you will be prompted for the password. The text
+ box does not hide the characters you type at this point--so make sure no one is
+ looking over your shoulder. The current implementation assumes that the password
+ for the keystore is also the password for the private key of the client you want
+ to authenticate as.
+
+ </p>
+ <p >
+
+ The next time you run your test, the SSL Manager will examine your key store to
+ see if it has more than one key available to it. If there is only one key, SSL
+ Manager will select it for you. If there is more than one key, you will be prompted
+ to select the alias you wish to authenticate as. If SSL Manager cannot detect
+ any keys in your keystore, it will give you a text box for the off chance you know
+ something it doesn't. Keep in mind that for the first run, you will be prompted
+ once per thread. Try to use only one thread for the first run to ensure everything
+ is working properly.
+
+ </p>
+ <b >
+ Things to Look Out For
+ </b>
+ <p >
+
+ You must have your Certificate Authority (CA) certificate installed properly
+ if it is not signed by one of the five CA certificates that ships with your
+ JDK. One method to install it is to import your CA certificate into a JKS
+ file, and name the JKS file "jssecacerts". Place the file in your JRE's
+ lib/security folder. This file will be read before the "cacerts" file in
+ the same directory. Keep in mind that as long as the "jssecacerts" file
+ exists, the certificates installed in "cacerts" will not be used. This may
+ cause problems for you. If you don't mind importing your CA certificate into
+ the "cacerts" file, then you can authenticate against all of the CA certificates
+ installed.
+
+ </p>
+ </td></tr>
<tr><td><br/></td></tr>
</table>
<hr>
1.13 +5 -0 jakarta-jmeter/docs/usermanual/get-started.html
Index: get-started.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/get-started.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- get-started.html 7 Mar 2002 23:03:12 -0000 1.12
+++ get-started.html 11 Mar 2002 22:19:58 -0000 1.13
@@ -278,6 +278,11 @@
by registering the SSL Provider.
</p>
<p >
+ There is also the
+ <a href="../usermanual/component_reference.html#SSL_Manager">SSL Manager</a>
+ , for greater control of certs.
+ </p>
+ <p >
Note: if you are running JDK1.4, then you do not have to download JSSE because Sun integrated it into JDK1.4 as a standard library.
</p>
</blockquote>
1.12 +54 -0 jakarta-jmeter/xdocs/usermanual/component_reference.xml
Index: component_reference.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- component_reference.xml 6 Mar 2002 03:52:03 -0000 1.11
+++ component_reference.xml 11 Mar 2002 22:19:58 -0000 1.12
@@ -802,6 +802,60 @@
as a graph with multiple lines. Each line represents a different HTTP Request from your test and
its response times.</p></description>
</component>
+
+<component index="13.7.2" name="SSL Manager" screenshot="">
+<p>
+ The SSL Manager is a way to select a client certificate so that you can test
+ applications that use Public Key Infrastructure (PKI). In order to use it,
+ you must have JSSE 1.0.2 installed. Unfortunately, there is no standard method
+ for controling who a client is--and that won't be introduced until JDK 1.4 is
+ officially available. The SSL Manager should still work with JDK 1.4, so this
+ is the best solution we could come up with.
+</p>
+
+<b>Choosing a Client Certificate</b>
+<p>
+ You may either use a Java Key Store (JKS) format key store, or a Public Key
+ Certificate Standard #12 (PKCS12) file for your client certificates. There
+ is a bug in the JSSE libraries that require you to have at least a six character
+ password on your key (at least for the keytool utility that comes with your
+ JDK).
+</p>
+<p>
+ To select the client certificate, choose Options->SSL Manager from the menu bar.
+ You will be presented with a file finder that looks for PKCS12 files by default.
+ Your PKCS12 file must have the extension '.p12' for SSL Manager to recognize it
+ as a PKCS12 file. Any other file will be treated like an average JKS key store.
+ If JSSE is correctly installed, you will be prompted for the password. The text
+ box does not hide the characters you type at this point--so make sure no one is
+ looking over your shoulder. The current implementation assumes that the password
+ for the keystore is also the password for the private key of the client you want
+ to authenticate as.
+</p>
+<p>
+ The next time you run your test, the SSL Manager will examine your key store to
+ see if it has more than one key available to it. If there is only one key, SSL
+ Manager will select it for you. If there is more than one key, you will be prompted
+ to select the alias you wish to authenticate as. If SSL Manager cannot detect
+ any keys in your keystore, it will give you a text box for the off chance you know
+ something it doesn't. Keep in mind that for the first run, you will be prompted
+ once per thread. Try to use only one thread for the first run to ensure everything
+ is working properly.
+</p>
+<b>Things to Look Out For</b>
+<p>
+ You must have your Certificate Authority (CA) certificate installed properly
+ if it is not signed by one of the five CA certificates that ships with your
+ JDK. One method to install it is to import your CA certificate into a JKS
+ file, and name the JKS file "jssecacerts". Place the file in your JRE's
+ lib/security folder. This file will be read before the "cacerts" file in
+ the same directory. Keep in mind that as long as the "jssecacerts" file
+ exists, the certificates installed in "cacerts" will not be used. This may
+ cause problems for you. If you don't mind importing your CA certificate into
+ the "cacerts" file, then you can authenticate against all of the CA certificates
+ installed.
+</p>
+</component>
</section>
</body>
</document>
1.9 +1 -0 jakarta-jmeter/xdocs/usermanual/get-started.xml
Index: get-started.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/get-started.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- get-started.xml 6 Mar 2002 03:52:03 -0000 1.8
+++ get-started.xml 11 Mar 2002 22:19:59 -0000 1.9
@@ -66,6 +66,7 @@
implementation of SSL be provided (such as Sun's <a href="http://java.sun.com/products/jsse/index.html">Java Secure Sockets Extension -- JSSE</a>).
Include the necessary encryption packages in JMeter's <a href="#classpath">classpath</a>. Also, update <a href="#configuring_jmeter">jmeter.properties</a>
by registering the SSL Provider.</p>
+<p>There is also the <complink name="SSL Manager"/>, for greater control of certs.</p>
<p>Note: if you are running JDK1.4, then you do not have to download JSSE because Sun integrated it into JDK1.4 as a standard library.</p>
</subsection>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>