Re: WSE 3.0 UsernameOverTransport Problem

Hi Pablo,

Client side: usernameOverTransport
Server side: usernameOverTransport and requireActionHeader

--Scott

Pablo Cibraro [MVP] wrote:
Hi,

Which WSE policies are you using on the client and the service ?

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

<gramanero-spam@xxxxxxxxx> wrote in message
news:1158588656.563084.182580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am fairly new to WSE, in general, however I have read several
articles online and believe I have a fairly good grasp of it. I am
working on integrating WSE 3.0 into an web service. The web service is
a very simple web service for the purposes of testing WSE 3.0
UsernameOverTransport.

The problem that I am having is that I am getting the following
exception stack trace on the server side:

Microsoft.Web.Services3.Security.SecurityFault: UsernameToken is
expected but not present in the security header of the incoming
message.
at
Microsoft.Web.Services3.Design.UsernameOverTransportAssertion.ServiceInputFilter.ValidateMessageSecurity(SoapEnvelope
envelope, Security security)
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.ServerProtocolFactory.Create(Type
type, HttpContext context, HttpRequest request, HttpResponse response,
Boolean&amp; abortProcessing)

In doing a fair amount of Google searches, it looks like I am not the
only one having this issue. I am curious if anyone has been able to
resolve this issue.

I have verified that the client is in fact sending the Username token
to the web service. In fact, I have verified, based on the stack trace,
the the server side does in fact see a security header, for some reason
it is simply unable to locate the Username token in the security
header. According to the server side log files though, it does exist
prior to processing the message.

Any help would be greatly appreciated.

Thank you!!


.

Relevant Pages

  • Re: WSE 3.0 UsernameOverTransport Problem
    ... Usually WSE throws that exception when the WSE extension is not configured ... Server side: usernameOverTransport and requireActionHeader ... working on integrating WSE 3.0 into an web service. ... expected but not present in the security header of the incoming ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE 3.0 UsernameOverTransport Problem
    ... Usually WSE throws that exception when the WSE extension is not configured ... Server side: usernameOverTransport and requireActionHeader ... working on integrating WSE 3.0 into an web service. ... expected but not present in the security header of the incoming ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE 3.0, X.509, and ISA Server
    ... I'll continue research and test various permutations until I find one that works like we want, probably using a web server on the DMZ and WSE for message security. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Can WSE 3.0 do this for me?
    ... So if use UsernameOverTransport to do the authentication once then can I also ... use message layer encryption rather than transport layer. ... Cause in the WSE ... must encrypt at the transport layer. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • WCF DerivedToken
    ... I am trying to determine how I can use a WCF client to call a WSE 3.0 ... UserNameOverTransport forces the transport layer to be secured by HTTPS ...
    (microsoft.public.dotnet.framework.webservices)