[jboss-svn-commits] JBossWS SVN: r851 - branches/jbossws-1.0/docs/user-guide/project/en/modules/wssecurity

[jboss-svn-commits at lists.jboss.org]

Author: jason.greene at jboss.com
Date: 2006-08-28 13:11:11 -0400 (Mon, 28 Aug 2006)
New Revision: 851

Modified:
   branches/jbossws-1.0/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml
Log:
Make client keystore/trustore clearer, add properties docs


Modified: branches/jbossws-1.0/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml
===================================================================
--- branches/jbossws-1.0/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml	2006-08-28 16:38:00 UTC (rev 850)
+++ branches/jbossws-1.0/docs/user-guide/project/en/modules/wssecurity/wssecurity.xml	2006-08-28 17:11:11 UTC (rev 851)
@@ -286,11 +286,46 @@
          </orderedlist>
       </para>
 
-      <para>We did not specify a key store or trust store, because client apps instead use the wsse System properties instead. If this was a web or ejb client (meaning a webservice client in a war or ejb jar file), then we would have specified them in the client descriptor.</para>
+      <para>We did not specify a key store or trust store, because client apps instead use the wsse System properties instead. If this was a web or ejb client (meaning a webservice client in a war or ejb jar file), then we would have specified them in the client descriptor. In that case, the keystore/truststore tags are the same as the one specified in the server config.</para>
 
    </sect1>
-
    <sect1>
+      <title>Standalone Client System Properties</title>
+      <para>If the client is standalone (not running within the container), then you need to specify the keystore and truststore values as system properties. They are as follows:</para> 
+   
+     <table frame="all">
+      <title>Standlone Client System Properties</title>
+      <tgroup cols="2">
+        <tbody>
+          <row>
+            <entry>org.jboss.wsse.keyStore</entry>
+            <entry>The keystore file.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.keyStorePassword</entry>
+            <entry>The password for the keystore.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.keyStoreType</entry>
+            <entry>The type of the keystore (JKS, pkcs12, etc).</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.trustStore</entry>
+            <entry>The trust store. It must contain the certs for any peer that communicates with the service.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.trustStorePassword</entry>
+            <entry>The password for the truststore.</entry>
+          </row>
+          <row>
+            <entry>org.jboss.wsse.trustStoreType</entry>
+            <entry>The type of the truststore (JKS, pkcs12, etc).</entry>
+          </row>
+        </tbody>
+      </tgroup>
+     </table>
+   </sect1>
+   <sect1>
       <title>SOAP message exchange</title>
 
       <para>Below you see the incomming SOAP message with the details of the security headers ommited. The idea is, that the SOAP body is still
@@ -355,4 +390,4 @@
          correctly and it still doesn't work chances are you have added the provider to the installation not being used.
       </para>
    </sect1>
-</chapter>
\ No newline at end of file
+</chapter>