Greetings

I'm implementing a secure webservice client using wss4j wich is supposed to use only signature Soap messages (I'm using it to communicate with a public webservice server). In the beginning I had the following problem:

faultString: WSDoAllReceiver: security processing failed (actions number mismatch)

After searching for a while I discovered that if the server is implemented in .NET, it always needs the message to be timestamped. So, just in case it was the reason of the problem (and while they send me the correct specification), I tried to add timestaping to the actions of the WSDoAllSender with the following order:

   <parameter name="action" value="Signature Timestamp"/>

and then the error is different, now it says:

   WSDoAllReceiver: security processing failed; nested exception is:
org.apache.ws.security.WSSecurityException: An error was discovered processing the <wsse:Security> header. (WSSecurityEngine: Invalid timestamp {0}); nested exception is: java.text.ParseException: Unparseable date: "2008-09-18T14:29:10.722Z"

that looks like the timestamp format is not correct. I was thinking that maybe the problem was the time location difference, but i've seen on the internet that in that case the error is different (and can be solved by the "timetolive" parameter). I tried to put the "Signature" and "Timestamp" in opposite way but I get the same error.

Could anybody help me?

Thank you very much

--
Un saludo,

Tomás Tormo Franco

Indenova, S.L.
Tels.: +34 963 81 99 47  ext.519
http://www.indenova.com
mailto:[EMAIL PROTECTED]

Reply via email to