Home Page › Forums › BizTalk 2004 – BizTalk 2010 › WCF calling SOAP with WS-Security .asmx external web service
- This topic has 1 reply, 1 voice, and was last updated 9 years, 7 months ago by
community-content.
-
AuthorPosts
-
-
November 3, 2009 at 11:32 AM #23636
Everything I’ve found so far says I should be able to use WCF to call a .asmx web service that uses WS-Security. The question is how to configure the WCF-Port. I’m using WCF-BasicHttp. First of all, is that okay? Second, how to enter the user/pass properly. On the security tab, which “Security Mode” should I pick?
The only one that seems to let me enter credentials is TransportWithMessageCredential, then I can click the “Edit” button by username credentials and enter a user/pass.
But when I run I got this:
<soap:Fault xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/”><faultcode xmlns:q0=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd”>q0:Security</faultcode><faultstring>Microsoft.Web.Services3.Security.SecurityFault: Security requirements are not satisfied because the security header is not present in the incoming message.
at Microsoft.Web.Services3.Design.UsernameOverTransportAssertion.ServiceInputFilter.ValidateMessageSecurity(SoapEnvelope envelope, Security security)
at MSB.RCTExpress.Presentation.Web.UsernameOverTransportAssertion.ServiceInputFilter.ValidateMessageSecurity(SoapEnvelope envelope, Security security) in C:\projects\la1safe1\RCT Express\MSB.RCTExpress\3.10\Presentation.Web\UsernameOverTransportNoSendNone.cs:line 27
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)</faultstring><faultactor>http://rct3.msbexpress.net/demo/ExpressLync/ValuationService.asmx</faultactor></soap:Fault>Any ideas?
Thanks,
Neal Walters -
November 3, 2009 at 3:06 PM #23640
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.