New to WCF, client passing username token with mustUnderstand set to true?

Your binding is basicHttpBinding You need to use wsHttpBinding.

Your binding is basicHttpBinding. You need to use wsHttpBinding.

1 @JohnSaunders because he is most likely barking up the right tree here. Is your client . NET/WCF?

If not, it may not be implementing WS-Security, or at least not in the way WCF wants it to. If the client is . NET, this is just an mismatched binding on the client side.

The mustUnderstand flag says that the WS-Security header must be acknowledged and processed. A non-WS-Security client, whether it's because it doesn't speak WS-Security or isn't configured to, will ignore the header, try to use the message anyway and the server will punt. Your other option is to turn of repudiation on the server.It'll stop sending WS-Security headers.

Of course, then you don't get repudiation.

I'm fairly certain it's a java client, but I don't know which flavor. – w s Nov 8 at 8:00.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.