Rampart > C

We all know that it is possible to use the feature known as 'Username tokens' in Apache Rampart/C to "Authenticate" a user. This feature can be used to verify if a user has access to a given system or not. Security requirements of a service does not end there. A system cannot grant carte blanche access blindly to its users. It needs to be more specific on credentials. For example, both Alice and Bob are in the system but only Alice can access my personal details.

Rampart/C is the security module of the Apache Axis2/C web services engine. The following tutorial by Kaushalye Kapuruge will guide you on how to configure Rampart/C in order to satisfy different security requirements in SOAP message exchanges.

Ever thought of how you can guarantee the safe delivery of SOAP messages? Do you know whether villains are spying on open channels? Maybe it's time to open your eyes. With simple configuration settings, you can now provide authenticity, data integrity, and non-repudiation to SOAP messages. The following article by Kaushalye Kapuruge explains how to provide SOAP message signatures using Rampart/C.

Apache Rampart/C is the security module of the Apache Axis2/C engine, which uses OMXMLSecurity as the XML-Security library. In this article, Kaushalye Kapuruge gives a clear view of the architecture of Rampart/C and OMXMLSecurity.

Apache Rampart/C has been implemented to support secure messaging for the Apache Axis2/C SOAP engine. In this interview, Kaushalye explains the finer points of Rampart/C and its relationship with Rampart/Java.