Thanks Prabhat. I tried with Axis2 version 1.5 but encountered the same issue. I have not tried the nightly build yet.
Thanks, Rajan -----Original Message----- From: Prabath Siriwardena [mailto:[email protected]] Sent: Friday, October 16, 2009 11:50 AM To: [email protected] Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted Yes - this is fixed in the Axis2 trunk - so the fix was not available with 1.4.1 Thanks & regards. -Prabath [1]:https://issues.apache.org/jira/browse/RAMPART-164 [2]:https://issues.apache.org/jira/browse/AXIS2-4241 Prabath Siriwardena wrote: > AFAIR this issue was fixed after after 1.4.1 release. > > I'll verify it for sure and let you know. > > Thanks & regards. > -Prabath > > Rajan Gupta wrote: >> Thanks Prabhat for the reply. I am using Axis2 version 1.4.1. Below is >> an extract from my axis2.xml. I see that I already have "Security" in my >> OutFaultFlow. >> <phaseOrder type="OutFaultFlow"> >> <!-- user can add his own phases to this area --> >> <phase name="soapmonitorPhase"/> >> <phase name="OperationOutFaultPhase"/> >> <phase name="RMPhase"/> >> <phase name="PolicyDetermination"/> >> <phase name="MessageOut"/> >> <phase name="Security"/> >> </phaseOrder> >> >> Is this functionality supposed to work in Axis2 1.4.1. Upgrading to >> Axis2 1.5 might not be possible for the time being. >> Thanks, >> Rajan >> -----Original Message----- >> From: Prabath Siriwardena [mailto:[email protected]] Sent: Friday, >> October 16, 2009 10:08 AM >> To: [email protected] >> Subject: Re: Axis2 with Rampart 1.4 - Faults are not getting encrypted >> >> Hi Rajan; >> >> Security will be applied to all the 'application faults' if you have >> defined the 'Security' phase under OutFaultFlow in the axis2.xml of >> the service end. >> >> What is the version of Axis2 you use ? Can you please try with Axis2 1.5 >> ? >> >> Thanks & regards. >> - Prabath >> >> Rajan Gupta wrote: >> >>> Hi, >>> >>> I am using axis2 with rampart version 1.4. When the operation is >>> successful the response from the server is encrypted, contains >>> required security headers, and works fine. In case when the >>> operation results in a fault, the server sends a clear text >>> response, similar to >>> >> >> >>> a response you would get without engaging rampart. The client is >>> expecting a secured response and hence fails. >>> >>> >>> >>> Is there anything special I need to do in rampart or axis2 >>> configuration for faults? >>> >>> >>> >>> Thanks in advance, >>> >>> Rajan >>> >>> >> >> >> > >
