Showing posts with label WS-SecurityPolicy. Show all posts
Showing posts with label WS-SecurityPolicy. Show all posts
Tuesday, June 24, 2008
Web Services Security with Apache Rampart – Part 2 (Message-Level Security)
Sometime back I blogged about Nandana's article on using transport level security with Apache Rampart policy based configuration. Here's the part two of the article which talks about using WS-SecurityPolicy to apply and enforce message level on SOAP messages using Apache Axis2 and Apache Rampart.
Thursday, March 13, 2008
Thursday, September 06, 2007
Apache Rampart 1.3 Released
This is the 1.3 release of Apache Rampart.
Apache Rampart 1.3 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis2 1.3, based on Apache WSS4J 1.5.3 and the Apache AXIOM-DOOM 1.2.5 implementations.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/rampart/1_3
There are two main Apache Axis2 modules provided with this release.
* rampart-1.3.mar
This provides support for WS-Security and WS-SecureConversation
features.
* rahas-1.3.mar
This module provides the necessary components to enable SecurityTokenService functionality on a service.
Apache Rampart 1.3 uses a configuration model based on WS-Policy and WS-Security Policy. It is important to note that the Apache Rampart 1.0 style configuration is also available even though being marked as deprecated.
Apache Rampart 1.3 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.3 to configure WS-SecureConversation + WS-ReliableMessaging scenarios.
The rampart module was successfully tested for interoperability with other WS-Security implementations.
WS - Sec* specifications supported by Apache Rampart are as follows:
* WS - Security 1.0
* WS - Secure Conversation - February 2005
* WS - Security Policy - 1.1 - July 2005
* WS - Trust - February 2005
* WS - Trust - WS-SX spec - EXPERIMENTAL
Thank you for using Apache Rampart.
Apache Rampart team
Apache Rampart 1.3 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis2 1.3, based on Apache WSS4J 1.5.3 and the Apache AXIOM-DOOM 1.2.5 implementations.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/rampart/1_3
There are two main Apache Axis2 modules provided with this release.
* rampart-1.3.mar
This provides support for WS-Security and WS-SecureConversation
features.
* rahas-1.3.mar
This module provides the necessary components to enable SecurityTokenService functionality on a service.
Apache Rampart 1.3 uses a configuration model based on WS-Policy and WS-Security Policy. It is important to note that the Apache Rampart 1.0 style configuration is also available even though being marked as deprecated.
Apache Rampart 1.3 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.3 to configure WS-SecureConversation + WS-ReliableMessaging scenarios.
The rampart module was successfully tested for interoperability with other WS-Security implementations.
WS - Sec* specifications supported by Apache Rampart are as follows:
* WS - Security 1.0
* WS - Secure Conversation - February 2005
* WS - Security Policy - 1.1 - July 2005
* WS - Trust - February 2005
* WS - Trust - WS-SX spec - EXPERIMENTAL
Thank you for using Apache Rampart.
Apache Rampart team
Tuesday, April 24, 2007
WSO2 WSAS and WS-SX:WS-SecurityPolicy-1.2
WSO2 WSAS successfully completed Round3 of the WS-Policy interop. The WS-SecurityPolicy implementation of WSAS is from Apcahe Neethi2 and Aapche Rampart.
This interop used the WS-SecurityPolicy-1.2 specification from the OASIS WS-SX TC.
The WSO2 interop endpoints can be found here
This interop used the WS-SecurityPolicy-1.2 specification from the OASIS WS-SX TC.
The WSO2 interop endpoints can be found here

Subscribe to:
Posts (Atom)