Hi, Could you kindly let me know if you have tested (or know if it will work) a situation where:
A service client connects to Rahas (STS), obtains a SamlToken by calling the RequestSecurityToken and using Rampart, places the SamlToken in the header of a SOAP message to a target service? Finally, would such a scenario work if Sandesha2 was brought into the mix for RM? Appreciate any information. - nagi On 9/7/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > 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 > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
