NonStop SOAP 4.1 User's Manual

4. Providing Rampart specific configuration details
Rampart module uses RampartConfig assertion to provide Rampart specific configuration
details to Rampart Engine. You can use this configuration to specify the username, password
type, path to the password provider library, and the path to certificates used for signing and
encryption. Based on your security requirements, you can add the required RampartConfig
assertions to the security policies. For more information about Rampart configuration assertions,
see “Rampart Specific Assertions ” (page 275).
5. Applying the security policy
You can use the service descriptor services.xml file to engage the Rampart module and
to apply the security policy to the Web service. The services.xml file is located at
<Nonstop SOAP 4 Deployment Directory>/services/<service_name>.
To engage the Rampart module, you must add the element <module ref=”rampart”/> in
services.xml file.
To apply the security policy, add the policy that you have created for the service in the
services.xml file.
The following sample shows the rampart enabled and security policy enabled services.xml
file:
<service name="sec_echo1">
<parameter name="ServiceClass" locked="xsd:false">sec_echoparameter name="ServiceClass"
locked="xsd:false">sec_echo</parameter>
<description>This is a testing service.description>This is a testing service.</description>
<module ref="rampart"/>
<operation name="echoString">
<parameter name="wsamapping">http://example.com/ws/2004/09/policy/Test/EchoRequest</parameter>
</operation>
<wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<!--Your policies are here-->
</wsp:Policy>
</service>
You can also engage the Rampart module for all the Web services by adding<module
ref=”rampart”/> in axis2.xml. The axis2.xml is located at <NonStop SOAP 4
deployment directory>.
The following sample displays the axis2.xml file with rampart module enabled:
<axisconfig name="Axis2/C">
.......
<!-- ============= -->
<!-- Global Modules -->
<!-- ============= ->
.....
<module ref="rampart"/>
.....
</axisconfig>
If you add <module ref="rampart"/> element in axis2.xml, then you need not add this
element in services.xml.
6. Restart the NonStop SOAP 4 server.
OSS>./<iTP WebServer Deployment Directory>/conf/restart
NOTE: If the service is regenerated through SoapAdminCL, the security policies in the
services.xml are removed.
Rampart Specific Assertions
Rampart specific policy assertions can be used along with WS-SecurityPolicy assertions while
securing the services.
Table 23 displays the RampartConfig assertions:
Rampart Specific Assertions 275