Hi Nandana, Jose, You were right about the timeskew element! I finally got it to work and it appears the client machine was 8 mins faster than the service machine. Thanks once again for both your help.
Regards Sanjay ________________________________ From: Nandana Mihindukulasooriya [mailto:[EMAIL PROTECTED] Sent: 24 July 2008 11:26 To: axis-user@ws.apache.org Subject: Re: Timestamp error when invoking a Rampart service from a .NET client. Hi Sanjay, In deed this seems to be a clock synchonization issue as pointed out by Jose. As it seems this fails when the Rampart validates the created element. As it seems created value contains a future time w.r.t the server machine. You can adjust a skew value to get over from that issue using the timestampMaxSkew [1] parameter in the Rampart Configuration. Anyway, I hope the following timestamps your posted are not generated at the same time. It seems to have a huge difference. SOAP Request from your .NET client ################################ <wsse:Security> <wsu:Timestamp wsu:Id="Timestamp-74569579-8e34-407f-a10c-c27d3b119b80"> <wsu:Created>2008-07-23T14:55:04Z</wsu:Created> <wsu:Expires>2008-07-23T15:00:04Z</wsu:Expires> </wsu:Timestamp> </wsse:Security> ### Java ### <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="Timestamp-1035988"> <wsu:Created>2008-07-24T08:59:27.952Z</wsu:Created> <wsu:Expires>2008-07-24T09:04:27.952Z</wsu:Expires> </wsu:Timestamp> thanks, nandana
