Error in WCF client consuming Axis 2 web service with WS-Security UsernameToken PasswordDigest authentication scheme?

I can confirm that the UPDATE from my question actually works.

I can confirm that the UPDATE from my question actually works: object IClientMessageInspector. BeforeSendRequest(ref System.ServiceModel.Channels. Message request, System.ServiceModel.

IClientChannel channel) { UsernameToken ut = new UsernameToken("USERNAME", "PASSWORD", PasswordOption. SendHashed); XmlElement securityElement = ut. GetXml(new XmlDocument()); MessageHeader myHeader = MessageHeader.

CreateHeader("Security", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd", securityElement, false); request.Headers. Add(myHeader); return Convert. DBNull; } And the client: CustomBehavior behavior = new CustomBehavior("USERNAME", "PASSWORD"); client.Endpoint.Behaviors.

Add(behavior); The error message was unrelated. The security header works with a very simple basicHttpBinding: Code sample of this in action can be found on my blog: http://blog.benpowell.co.uk/2010/11/supporting-ws-i-basic-profile-password.html.

I had a similar problem recently and gave up searching for a non-WSE solution. After a couple days of pulling my hair out I ended downloading the WSE 3.0 SDK, generating a proxy class using WseWsdl3. Exe, and creating a new policy for the UsernameToken.

I was up and running in 15min. The following is currently working for me. RemoteService service = new RemoteService(); //generated class UsernameToken token = new UsernameToken(username, password, PasswordOption.

SendPlainText); Policy policy = new Policy(); policy.Assertions. Add(new UsernameOverTransportAssertion()); service. SetClientCredential(token); service.

SetPolicy(policy); var result = service.MethodCall().

This question is well written -- many thanks. In reference to @Junto's "How do I use this" comment, it turns out that the SecurityHeader param on the service method can be used to add the header. I've included an example below.

I believe that what's happening is that the SvcUtil. Exe tool is barfing when trying to read the WS* DTDs. This is not obvious when you use the "Add Service Reference" wizard.

But it is very obvious when you run svcutil. Exe from the command line. Because svcutil.

Exe fails to read the WS* DTD's, the SecurityHeader object is not well developed. But Microsoft gives you an out with the . Any property.

You can serialize the UsernameToken class right into the . Any property and your header will be added to the message. Again, thanks for this excellent question.

How to use the SecurityHeader parameter to add a UsernameToken security header: Required tools: Fiddler2 (or similar) -- you really can't figure any of this out without inspecting the http headers. Required Reference: Microsoft.Web. Services3.

Dll -- you can reference this 2.0 framework assembly from your 4.0 assembly WCF service call: // Initialization of the service... _service = new MyService("MyEndpoint", RemoteUri); // etc. // Calling the service -- note call to GetSecurityHeader() _service. ServiceAction(GetSecurityHeader(), "myParam1"); // etc./// /// Construct the WSE 3.0 Security Header /// private SecurityHeader GetSecurityHeader() { SecurityHeader h = new SecurityHeader(); UsernameToken t = new UsernameToken(RemoteLogin, RemotePassword, PasswordOption. SendPlainText); h.

Any = new XmlElement1; h. Any0 = t. GetXml(new XmlDocument()); return h; } App.config.

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.