Hi Håkon,

We could not get the SAML 2.0 support with the WSS4J 1.5.8 release.
Hopefully, we will be able to get it by WSS4J 1.5.9 release.

Thanks,
/thilina


Thilina Mahesh Buddhika
http://blog.thilinamb.com


2010/2/3 Håkon Sagehaug <[email protected]>

> Hi
>
> Does wss4j support SAML2 also? I downloaded the latest release, wss4j
> 1.5.8,
> u tcould not find any reference to SAML 2.0, not a prosessor.  I've followd
> this issue [1] but I can't see it refelcted in the code.
>
> Håkon
>
> [1]https://issues.apache.org/jira/browse/WSS-204
>
> On 2 February 2010 18:06, Nandana Mihindukulasooriya <[email protected]
> >wrote:
>
> > Apache Rampart team is pleased to announce the 1.5 release of Apache
> > Rampart
> > module.
> >
> > Apache Rampart is the the security module of Axis2 which provides
> > implementations of the WS-Sec* specifications for Apache Axis2.  Apache
> > Rampart 1.5 release is compatible with Axis2 1.5 / 1.5.1 releases. Please
> > refer to http://ws.apache.org/rampart/ for more information.
> >
> > You can download the release from:
> > http://ws.apache.org/rampart/download/1.5/download.cgi
> >
> > Apache Rampart supports the following specifications:
> > * WS - Security 1.0 / 1.1
> > * WS - Security Policy - 1.1 / 1.2
> > * WS - Secure Conversation - February 2005 / WS-SX
> > * WS - Trust - February 2005 / WS-SX
> > * SAML 1.1 / 2.0
> >
> > Apache Rampart 1.5 can be successfully used with the next Apache
> Sandesha2
> > release targeted towards Apache Axis2 1.5 to configure
> > WS-SecureConversation
> > + WS-ReliableMessaging scenarios.
> >
> > New features of Apache Rampart 1.5 includes
> > * SAML 2.0 support
> > * Key store caching
> > * Signing / Encrypting with multiple keys
> > * Tests for negative scenarios
> >
> > We welcome any and all feedback at:
> > Issue Tracker : http://issues.apache.org/jira/browse/Rampart
> > Mailing List     : [email protected]
> >
> > Thank you for your interest in Apache Rampart!
> >
> > The Rampart Development Team
> > http://ws.apache.org/rampart/
> >
>

Reply via email to