This document guides you on how to install Rampart/C.
You must have OpenSSL 0.9.8 (or above) installed in you system.
This release comes in two forms, source and binary. This document covers both forms.
Please send your feedback to the developer mailing list: rampart-c-dev@ws.apache.org (Subscription details are available on the Rampart/C site.
This can be done using binary or source distributions. (Download the two distributions)
The following steps have to be followed to install and run the Rampart/C binary distribution on Linux :
The following steps have to be followed to install and run Rampart/C using the source distribution on Linux :
This too can be done using binary or source distributions. (Download the two distributions.)
(Note: You can download the Microsoft VSExpress2005 edition and Platform SDK from the Microsoft Web site. You will need to add the path to the Platform SDK Include and Lib folders to the makefile)
The following steps will take you through the source compilation.
(Note: You may have to set the PATH environment variable to vcvars32.bat if MS Windows gives an error indicating that it cannot find this batch file. This file is located in <your MS Visual Studio install Directory>\VC\bin directory.)
You can engage Rampart/C in global level or in service level.
Just add the following entry either to axis2.xml(gloabl level) or in services.xml(service level) corresponding to the service you want to secure.
<module ref="rampart"/>
Apart from that you must define security policies for outgoing messages and incoming messages. This can be done by adding parameters in the same descriptor file that you engaged rampart as follows.
<parameter name="OutflowSecurityPolicy">/your/path/to/outgoing-secpolicy.xml</parameter> <parameter name="InflowSecurityPolicy">/your/path/to/incoming-secpolicy.xml</parameter>
NOTE: There are several sample security policy xml files for different scenarios under samples/secpolicy/. Please refer to the README file inside this folder for more information.
The final configuration setup should be as follows:
CLIENT SIDE:In axis2.xml
<module ref="rampart"/> <parameter name="OutflowSecurityPolicy">/../../outgoing-secpolicy.xml</parameter> <parameter name="InflowSecurityPolicy">/../../incoming-secpolicy.xml</parameter>SERVER SIDE:
In services.xml(or axis2.xml)
<module ref="rampart"/> <parameter name="OutflowSecurityPolicy">/../../outgoing-secpolicy.xml</parameter> <parameter name="InflowSecurityPolicy">/../../incoming-secpolicy.xml>/parameter>
NOTE: Please find sample security policy files that are located under samples/secpolicy
You may go to each and every scenario and see how Rampart/C is configured using the policy assertions available in respective policy files.
For each scenario there are four policy files:
NOTE: If you have changed an outgoing policy file, make sure that you change the corresponding incoming policy file as well, and vise versa.