>I was doing some interropability testing between .NET and AXIS. .NET is
consumer and AXIS
>is provider which uses WSS4J for implementing digital signatures. When
the consumer signs
>a soap message and when I try to verify the signature using WSS4J on
the provider side
>I am getting an error like "digest value mismatch".
>I think the message when it is sent to the provider, it somehow got
modified after
>it is signed and this causing signature verification failure error on
the provider side.
Correct.
>I am not sure how to solve this error. Does anybody have ideas for me
here ....
This configuration in the globalCOnfiguration of server-config.wsdd
works fine for me with .NET clients:
<parameter name="enableNamespacePrefixOptimization" value="false"/>
<parameter name="disablePrettyXML" value="false"/>
Solved this problem I encountered with .NET client an "actions mismatch"
error due to the different position of Timestamp in the WSS header
generated by WSE 2.0.
So for using the "Timestamp Signature" for action I had to extend
WSDoAllReceiver and override the invoke method commenting out this lines
of code:
/*
* now check the security actions: do they match, in right order?
*/
/*
if (!checkReceiverResults(wsResult, actions)) {
throw new AxisFault(
"WSDoAllReceiverNoActionOrderCheck: security processing failed
(actions mismatch)");
}
*/
Regards,
Luciano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
