Thank you for the interest you are showing in my problem !

I'll quote below WSS4J's official Wiki:

"Problems and errors with Signature verification
...
Most often this problem occurs if the request message was modified after it
was signed. Mostly this is due to some pretty printing where the request
message was modified to look nicer. This pretty printing inserts newlines,
blanks and tabs. Very often people think that these additional charaters are
removed by canonicalization (c14n) of the message. This is a common
misunderstanding."

http://wiki.apache.org/ws/FrontPage/WsFx/wss4jFAQ

Accordingly I think that "canonicalization" won't solve my problem.
That's why I was searching how to deactivate the component on server's side
That performs this pretty print. 

I do know that .Net sends the message into one line:

<soap:Body wsu:Id="Id-2d57b233-8b17-4ccb-afc5-8bbc6b8f33e7"><Show_Request
xmlns="http://box.types.ws.temip.ov.hp.com";><EntitySpec><Natural>BOX
a</Natural></EntitySpec></Show_Request></soap:Body>

Which is transformed afterward -on server's side- into this form:

<soap:Body wsu:Id="Id-2d57b233-8b17-4ccb-afc5-8bbc6b8f33e7">
  <Show_Request xmlns="http://box.types.ws.temip.ov.hp.com";>
   <EntitySpec>
    <Natural>
BOX a    </Natural>
   </EntitySpec>
  </Show_Request>
 </soap:Body>

NB: the signature is done only on the Body of SOAP Message.
__________________
Benjamin BALET
Capgemini France
http://bbalet.free.fr/

> OK, that's useful to know; thanks. But I thought that the canonicalization

> of the message, before signature and again when the signature is checked, 
> is supposed to avoid this. Maybe Axis doesn't do the canonicalization?
>
>Guy Rixon

>> Yes, pertty printing after Signature definitly invalidates the
>> Signature.
>>
>> Werner





This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.

Reply via email to