Hola Tomas!
Try using this parameter:
<parameter name="*disablePrettyXML*" value="true"/>
Although this is much for the signature, but you never know!
Un saludo
On Thu, Sep 18, 2008 at 4:47 PM, Nandana Mihindukulasooriya <
[EMAIL PROTECTED]> wrote:
> Hi Thomas,
> Are you using Axis2 or Axis ? I assume you are using Axis.
> There is a property in WSSConfig in WSS4J called precisionInMilliSeconds.
> You must be able to set it to false using configuration. Sometimes having
> mili second precision in the time stamp cause a problem in the .NET side.
>
> thanks,
> nandana
>
>
> On Thu, Sep 18, 2008 at 8:05 PM, Tomás Tormo <[EMAIL PROTECTED]> wrote:
>
>> 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.519http://www.indenova.commailto:[EMAIL
>> PROTECTED] <[EMAIL PROTECTED]>
>>
>>
>
>
> --
> Nandana Mihindukulasooriya
> WSO2 inc.
>
> http://nandana83.blogspot.com/
> http://www.wso2.org
>
--
Jose Ferreiro
EPFL Communication Systems engineer
ing.sys.com.dipl.EPFL
