The reason Rampart doesn't support SwA security is not solved by a little bit of policy! The problem is that Rampart is based on XML security and the SwA message is not in XML. A much simpler solution is to move to use MTOM which is more interoperable and is fully supported in every aspect by Rampart.
Paul On Dec 14, 2007 5:49 PM, Jayavarshini Radhakrishnan <[EMAIL PROTECTED]> wrote: > Hi, > > We have implemented Axis2 for trading SOAP messages. As described by > Axis2, we are using the Rampart module and Neethi policy to implement SOAP > security. However, Rampart doesn't support SwA(SOAP with Attachment) > security. Hence, I am trying to create a custom policy, which I can add it > as policy component to Neethi. However, I am unable to get any guidelines > for creating policy for securing attachments. I am new to this, so If I am > on the wrong track, please let me know. Any help/guidelines would be > appreciated. > > Thanks, > Jaya -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com
