You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ch...@apache.org on 2007/01/10 06:58:22 UTC
svn commit: r494727 -
/webservices/axis2/branches/java/1_1/xdocs/modules/rampart/1_1/security-module.html
Author: chatra
Date: Tue Jan 9 21:58:20 2007
New Revision: 494727
URL: http://svn.apache.org/viewvc?view=rev&rev=494727
Log:
corrected contents section
Modified:
webservices/axis2/branches/java/1_1/xdocs/modules/rampart/1_1/security-module.html
Modified: webservices/axis2/branches/java/1_1/xdocs/modules/rampart/1_1/security-module.html
URL: http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_1/xdocs/modules/rampart/1_1/security-module.html?view=diff&rev=494727&r1=494726&r2=494727
==============================================================================
--- webservices/axis2/branches/java/1_1/xdocs/modules/rampart/1_1/security-module.html (original)
+++ webservices/axis2/branches/java/1_1/xdocs/modules/rampart/1_1/security-module.html Tue Jan 9 21:58:20 2007
@@ -16,8 +16,17 @@
<h2>Content</h2>
<ul>
<li><a href="#intro">Introduction</a></li>
+ <li><a href="#1.1_config">Rampart-1.1 Configuration</a>
+ <ul>
+ <li><a href="#1.1_assetions">Rampart Specific Assertions</a></li>
+ <li><a href="#1.1_service_config">Service Configration</a></li>
+ <li><a href="#1.1_client_config">Client Confiuration</a></li>
+ </ul></li>
+ <li><a href="#1.0_config">Rampart-1.0 Configuration</a>
+ <ul>
<li><a href="#outflowsecurity">OutflowSecurity Parameter</a></li>
<li><a href="#inflowsecurity">InflowSecurity Parameter</a></li>
+ </ul></li>
<li><a href="#references">References</a></li>
<li><a href="#examples">Examples</a></li>
</ul>
@@ -45,9 +54,9 @@
The configuration parameters should be set in the service.xml file of the
service. The client side config parameters should be set in the axis2.xml of
the client's Axis2 repository.</p>
-
+<a id="1.1_config"></a>
<h2>Rampart-1.1 Configuration</h2>
-
+<a id="1.1_assetions"></a>
<h3>Rampart Specific Assertions</h3>
<p>Rampart uses the standard WS-SecurityPolicy[2] assertions and also defines its own
@@ -58,13 +67,13 @@
<p>The <strong>ramp:RampartConfig</strong> assertion must be available as a one of the top
level assertions of the policy as shown <a href="sec-conf/sample-policy.xml">here</a>.</p>
-
+<a id="1.1_service_config"></a>
<h3>Service Configration</h3>
To configure the service one will simply have to add the policy element into the
sevices.xml file. A sample service.xml file is available
<a href="sec-conf/sample-services.xml">here</a>.
-
+<a id="1.1_client_config"></a>
<h3>Client Confiuration</h3>
<p>On the client side, a policy object should be created and loaded into options. Creating the policy object can be done using a "policy.xml" file as follows.</p>
@@ -76,13 +85,13 @@
Options options = new Options();
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, clientPolicy);
</pre>
-
+<a name="1.0_config"></a>
<h2>Rampart-1.0 Configuration</h2>
<p>Rampart module uses two parameters:</p>
<ul>
- <li>OutflowSecurity</li>
- <li>InflowSecurity</li>
+ <li><a href="outflowsecurity">OutflowSecurity</a></li>
+ <li><a href="inflowsecurity">InflowSecurity</a></li>
</ul>
The configuration that can go in each of these parameters are described
below: <a name="outflowsecurity"></a>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-cvs-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-cvs-help@ws.apache.org