Author: buildbot
Date: Mon Dec 10 18:31:45 2012
New Revision: 841478
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/ws-security-in-ode.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 10 18:31:45 2012
@@ -1 +1 @@
-1419635
+1419637
Modified: websites/staging/ode/trunk/content/ws-security-in-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/ws-security-in-ode.html (original)
+++ websites/staging/ode/trunk/content/ws-security-in-ode.html Mon Dec 10
18:31:45 2012
@@ -173,8 +173,8 @@
<p>Let's take an example and see the actual required steps.</p>
<h3 id="how-to-invoke-a-secure-web-service">How to invoke a secure web
service?</h3>
<h4 id="prepare-your-service-document">Prepare your service document</h4>
-<p>Assuming your process needs to invoke the secure service
{http://sample03.policy.samples.rampart.apache.org}Sample03, the <em>first
step</em> is to prepare a service document named
${process_bundle_dir}/Sample03.axis2 and containing your desired Rampart
configuration.
-The <em>second step</em> is to to make sure the resources needed to invoke the
services are available to Rampart through ODE webapp classpath. Typical
resources are:</p>
+<p>Assuming your process needs to invoke the secure service
{http://sample03.policy.samples.rampart.apache.org}Sample03, the <em>first
step</em> is to prepare a service document named
${process_bundle_dir}/Sample03.axis2 and containing your desired Rampart
configuration.</p>
+<p>The <em>second step</em> is to to make sure the resources needed to invoke
the services are available to Rampart through ODE webapp classpath. Typical
resources are:</p>
<ul>
<li>password callback handler classes</li>
<li>Java keystores</li>
@@ -187,15 +187,17 @@ The <em>second step</em> is to to make s
<li>ode/WEB-INF/lib</li>
</ul>
<h4 id="an-alternative-for-ws-security-policies">An alternative for
WS-Security Policies</h4>
-<p>If you're using the policy base configuration model, an alternative is
available to you: use the <a href="endpoint-configuration.html">endpoint
property mechanism</a> to attach the policy to the service. In that
configuration, ODE will engage the Rampart module and load the policy when the
service is invoked.
-To do so:
-<em> save the Policy document (not the service document) in the file of your
choice. For instance mypolicy.xml
-</em> create an endpoint file linking the service and the policy file.
Basically with the two properties listed below. Note that if the path assigned
to the "security.policy.file" property is relative it will be resolved against
the process bundle directory. Of course if the path is absolute, it will be
used as is.</p>
-<div
class="codehilite"><pre>alias.sample03-ns=http://sample03.policy.samples.rampart.apache.org
-sample03-ns.sample03-policy.ode.security.policy.file=mypolicy.xml
-</pre></div>
-
-
+<p>If you're using the policy base configuration model, an alternative is
available to you: use the <a href="endpoint-configuration.html">endpoint
property mechanism</a> to attach the policy to the service. In that
configuration, ODE will engage the Rampart module and load the policy when the
service is invoked.</p>
+<p>To do so:</p>
+<ul>
+<li>save the Policy document (not the service document) in the file of your
choice. For instance mypolicy.xml</li>
+<li>
+<p>create an endpoint file linking the service and the policy file. Basically
with the two properties listed below. Note that if the path assigned to the
"security.policy.file" property is relative it will be resolved against the
process bundle directory. Of course if the path is absolute, it will be used as
is.</p>
+<p>:::xml
+alias.sample03-ns=http://sample03.policy.samples.rampart.apache.org
+sample03-ns.sample03-policy.ode.security.policy.file=mypolicy.xml</p>
+</li>
+</ul>
<h3 id="how-to-secure-the-web-service-exposed-by-a-process">How to secure the
web service exposed by a process?</h3>
<p>Applying security to a process service is no different from invoking a
secured service. If the process service you're exposing is
{http://mycompany.com}AbscenceRequest. All you have to do is prepare a service
document named ${process_bundle_dir}/AbscenceRequest.axis2 and containing your
Rampart configuration. Once again, it's up to you to add the required resources
in ODE webapp classpath.</p>
<p>You can also use the property 'security.policy.file' to secure the process
service.</p>
@@ -217,33 +219,43 @@ $ buildr test:Secure
<h5 id="where-are-the-processes-executed-by-the-unit-tests">Where are the
processes executed by the unit tests?</h5>
-<p>The executed processes are generated by the build, so run the tests once,
then look into the following directories. Process directories are prefixed with
"process-".
-<em> axis2-war/target/test-classes/TestRampartPolicy/secured-services/
-</em> axis2-war/target/test-classes/TestRampartPolicy/secured-processes/
-<em> axis2-war/target/test-classes/TestRampartBasic/secured-services/
-</em> axis2-war/target/test-classes/TestRampartBasic/secured-processes/</p>
+<p>The executed processes are generated by the build, so run the tests once,
then look into the following directories. Process directories are prefixed with
"process-".</p>
+<ul>
+<li>axis2-war/target/test-classes/TestRampartPolicy/secured-services/</li>
+<li>axis2-war/target/test-classes/TestRampartPolicy/secured-processes/</li>
+<li>axis2-war/target/test-classes/TestRampartBasic/secured-services/</li>
+<li>axis2-war/target/test-classes/TestRampartBasic/secured-processes/</li>
+</ul>
<h5 id="the-nitty-gritty-details">the nitty-gritty details</h5>
<p>The integration with Rampart described in this section is tested with a
decent suite of unit tests. These unit tests are based on the <a
href="http://ws.apache.org/rampart/samples.html";>Rampart samples</a>. The <a
href="http://svn.apache.org/repos/asf/webservices/rampart/branches/java/1_3/modules/rampart-samples/";>related
resources</a> were imported into ODE repository.</p>
<p>These tests are divided into two parts: tests using the parameter base
configuration model aka "basic tests" and tests using the policy base
configuration model aka "policy tests".</p>
-<p>ODE test cases reuse these test cases in two different scenarii:
-<em> the security configuration is applied to an "external" web service, and a
ODE process invokes it.
-</em> the security configuration is applied to the web service exposed by a
process.</p>
-<p>These partitions lead to four resource directories:
-<em> <a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-services/";>TestRampartBasic/secured-services</a>
-</em> <a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-processes/";>TestRampartBasic/secured-processes</a></p>
+<p>ODE test cases reuse these test cases in two different scenarii:</p>
<ul>
-<li><a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartPolicy/secured-services/";>TestRampartPolicy/secured-services</a></li>
+<li>the security configuration is applied to an "external" web service, and a
ODE process invokes it.</li>
+<li>the security configuration is applied to the web service exposed by a
process.</li>
+</ul>
+<p>These partitions lead to four resource directories:</p>
+<ul>
+<li><a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-services/";>TestRampartBasic/secured-services</a></li>
+<li>
+<p><a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-processes/";>TestRampartBasic/secured-processes</a></p>
+</li>
+<li>
+<p><a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartPolicy/secured-services/";>TestRampartPolicy/secured-services</a></p>
+</li>
<li><a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartPolicy/secured-processes/";>TestRampartPolicy/secured-processes</a></li>
</ul>
<p>Everything describes for TestRampartBasic applies to TestRampartPolicy. So
for now on we will mention only TestRampartBasic.</p>
<p>For the "secured-services" scenario, the "external" web services are Axis
<a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-services/services/";>archives</a>
deployed in an Axis2 webapp.</p>
<p>The corresponding unit test classes are <a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/java/org/apache/ode/axis2/rampart/basic/";>SecuredServicesTest.java
and SecuredProcessTest.java</a>. Each test class will start a list of
processes that must succeed (as many processes as Rampart samples actually).</p>
<p>To avoid duplication these processes are generated by the build based on
two process templates: <a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-services/process-template/";>one</a>
for the secured-services case, <a
href="http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-processes/process-template/";>another</a>
for the secured-processes case.</p>
-<p>The build generates processes into:
-<em>
axis2-war/target/test-classes/TestRampartPolicy/secured-services/process-</em>
-<em>
axis2-war/target/test-classes/TestRampartPolicy/secured-processes/process-</em>
-<em>
axis2-war/target/test-classes/TestRampartBasic/secured-services/process-</em>
-<em>
axis2-war/target/test-classes/TestRampartBasic/secured-processes/process-</em></p>
+<p>The build generates processes into:</p>
+<ul>
+<li>axis2-war/target/test-classes/TestRampartPolicy/secured-services/process-*</li>
+<li>axis2-war/target/test-classes/TestRampartPolicy/secured-processes/process-*</li>
+<li>axis2-war/target/test-classes/TestRampartBasic/secured-services/process-*</li>
+<li>axis2-war/target/test-classes/TestRampartBasic/secured-processes/process-*</li>
+</ul>
</div>
</div>
