I have a WSE 3.0 Webservice that when I run it from a Java based Testing tool responds with the following.

It does not want to get past the Cipher Data in the Envelope, If I run my service without WSE the Service runs fine, as soon as I enable the X509 I get this, I found the following article, but I'm not sure how to implement it in my web.config.

http://support.microsoft.com/kb/922779/en-us?spid=8291&sid=1105




<soap:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
<wsa:MessageID>urn:uuid:d307a65f-8f4d-4377-88cd-60a86a238071</wsa:MessageID>
<wsa:RelatesTo>urn:uuid:71f0b327-1033-44a2-a81a-5346cdd99484</wsa:RelatesTo>
<wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
</soap:Header>
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring><![CDATA[System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.ApplicationException: WSE841: An error occured processing an outgoing fault response. ---> System.Web.Services.Protocols.SoapHeaderException: Microsoft.Web.Services3.Security.SecurityFault: Referenced security token could not be retrieved ---> System.InvalidOperationException: WSE590: Failed to resolve the following Key Info <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:Reference URI="#null" /></wsse:SecurityTokenReference></KeyInfo>.
--- End of inner exception stack trace ---
at Microsoft.Web.Services3.Security.EncryptedData.ResolveDecryptionKey(String algorithmUri, KeyInfo keyInfo)
at Microsoft.Web.Services3.Security.EncryptedData.Decrypt(XmlElement encryptedElement)
at Microsoft.Web.Services3.Security.EncryptedData.Decrypt()
at Microsoft.Web.Services3.Security.Security.LoadXml(XmlElement element)
at Microsoft.Web.Services3.Security.Security.CreateFrom(SoapEnvelope envelope, String localActor, String serviceActor)
at Microsoft.Web.Services3.Security.ReceiveSecurityFilter.ProcessMessage(SoapEnvelope envelope)
at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
at Microsoft.Web.Services3.WseProtocol.FilterRequest(SoapEnvelope requestEnvelope)
at Microsoft.Web.Services3.WseProtocol.RouteRequest(SoapServerMessage message)
at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response)
at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---]]></faultstring>
<faultactor>http://bis3y/assignmentservice.asmx</faultactor>
</soap:Fault>
</soap:Body>
</soap:Envelope>

---

Z

Were you aware that WSE is obsolete?

---

John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects

I have to match a Service that was previously developed by another company the, I have no choice but to develope it so it comes out as an ASMX Service.

Rob

---

Z

That's not true. You can probably use WCF to consume the WSE service. That's the way to go, and it doesn't give you a dependency on obsolete software.

---

John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects

Another Company is sending me XML Via a SOAP Services, they are Posting to a SOAP Service I Create have to Create, they are only able to POST to a Service Called AssignmentService.ASMX, and in this has a Service Name, is there a way to Create a WCF that would look to the other company as this.

Rob

---

Z

I don't know whether you can create a WCF service named .ASMX. You should ask on the WCF Forum .

The company which is sending to you should permit the flexibility of accepting an arbitrary URL to send to. There is no concept of a "file extension" in web services, so no meaning should be attached to the ".asmx". If they maintain this requirement, they will eventually be requiring their partners to work with unsupported software.

---

John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects