Easy way to disable the mustUnderstand attribute?

Jim McCafferty

10y6.5k

Hi,

I've implemented a console app which transmits information to a Java SOAP service, using certificate signing (but no encryption). With message level security, the service is complaining specifically about the mustUnderstand attribute on the security header.

I following the Microsoft example of implementing a Custom Message Text Encoder - in the write message function I converted the message to a string, performed a replace on MustUnderstand=1 to MustUnderstand=0 and converted the message back to a byte array.

The console application is currently transmitting about 80% of the messages, but occasionally security faults are being thrown. At the Write Message stage, the certificate has already signed the message, and I'm wondering if the MustUnderstand change is invalidating the signature. Also, the Service Admin have noticed there are a variable number of null characters after the Soap envelope (these are present in both successful and failing messages).

I initially tried modifying the message using a SOAP inspector implementation, but at that stage the security header had not been constructed. I have also implemented an asymmetric security binding element class. Is there a way to specific the mustunderstand attribute in here?

Thanks in advance

Jim

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Jim McCafferty9y ago
Hi Ramesh,

I tried this solution previously - the problem is at the point the Client Inspector is implemented the security headers are not available (see attached screenshot). I'm using this class currently to remove the VSCausalityData.

Best Wishes
Jim

UPDATE:
I've changed my custom text message encoder write message function to write out the message to an XElement - and using the remove attribute function to eliminate the mustUnderstand attribute. This works (inspecting the message) , but now the service is reporting premature end of file. The payload for the service function is XML, and I notice while inspecting the message the < and > characters have been replaced with > and <. I'm currently investigating a way of leaving the payload as raw XML...
0
Ramesh Kartik10y ago
Hello Jim,

You have to use IClientMessageInspector to disable/remove the header. Can you try like the source code i attached?

If am answered your question,please mark it as "ACCEPTED ANSWER"
0