Author: vanto
Date: Mon Dec 10 18:31:36 2012
New Revision: 1419637
URL: http://svn.apache.org/viewvc?rev=1419637&view=rev
Log:
fix formatting.
Modified:
ode/site/trunk/content/ws-security-in-ode.mdtext
Modified: ode/site/trunk/content/ws-security-in-ode.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/ws-security-in-ode.mdtext?rev=1419637&r1=1419636&r2=1419637&view=diff
==============================================================================
--- ode/site/trunk/content/ws-security-in-ode.mdtext (original)
+++ ode/site/trunk/content/ws-security-in-ode.mdtext Mon Dec 10 18:31:36 2012
@@ -100,6 +100,7 @@ Let's take an example and see the actual
#### Prepare your service document
Assuming your process needs to invoke the secure service
{http://sample03.policy.samples.rampart.apache.org}Sample03, the _first step_
is to prepare a service document named ${process_bundle_dir}/Sample03.axis2 and
containing your desired Rampart configuration.
+
The _second step_ is to to make sure the resources needed to invoke the
services are available to Rampart through ODE webapp classpath. Typical
resources are:
* password callback handler classes
@@ -114,7 +115,9 @@ How you add these resources to ODE class
#### An alternative for WS-Security Policies
If you're using the policy base configuration model, an alternative is
available to you: use the [endpoint property
mechanism](endpoint-configuration.html) 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:
+
* save the Policy document (not the service document) in the file of your
choice. For instance mypolicy.xml
* 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.
@@ -151,6 +154,7 @@ No. ODE comes with the following Axis2 m
##### Where are the processes executed by the unit tests?
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-".
+
* axis2-war/target/test-classes/TestRampartPolicy/secured-services/
* axis2-war/target/test-classes/TestRampartPolicy/secured-processes/
* axis2-war/target/test-classes/TestRampartBasic/secured-services/
@@ -163,10 +167,12 @@ The integration with Rampart described i
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".
ODE test cases reuse these test cases in two different scenarii:
+
* the security configuration is applied to an "external" web service, and a
ODE process invokes it.
* the security configuration is applied to the web service exposed by a
process.
These partitions lead to four resource directories:
+
*
[TestRampartBasic/secured-services](http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-services/)
*
[TestRampartBasic/secured-processes](http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-processes/)
@@ -182,6 +188,7 @@ The corresponding unit test classes are
To avoid duplication these processes are generated by the build based on two
process templates:
[one](http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-services/process-template/)
for the secured-services case,
[another](http://svn.apache.org/viewvc/ode/branches/APACHE_ODE_1.X/axis2-war/src/test/resources/TestRampartBasic/secured-processes/process-template/)
for the secured-processes case.
The build generates processes into:
+
* axis2-war/target/test-classes/TestRampartPolicy/secured-services/process-*
* axis2-war/target/test-classes/TestRampartPolicy/secured-processes/process-*
* axis2-war/target/test-classes/TestRampartBasic/secured-services/process-*
