WSE 3.0 - UsernameOverTransport Assertion

WSE 3.0 - UsernameOverTransport Assertion - SOAP Header Exception

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Anshu - 28 Nov 2006 19:52 GMT

I am trying to implement the UsernameOverTransport Assertion in WSE 3.0. I
will be authenticating against a .NET 2.0 Membership system, so I have
created a custom username token manager class.

I keep receiving the following exception from a test client app I created:

"System.Web.Services.Protocols.SoapHeaderException:
Microsoft.Web.Services3.Security.SecurityFault: UsernameToken is expected but
not present in the security header of the incoming message."

However, when I look at the output trace log from the client, I can see the
username token in the header of the SOAP message. It also appears in the
input trace log of the service.

Any thoughts on why the service does not recognize the UsernameToken? or
where to look?

Reply to this Message

Pablo Cibraro [MVP] - 29 Nov 2006 14:41 GMT

Hi Anshu,

You should check these three points first:

1. You are receiving the UsernameToken on the service side (Take a look to
the input trace on the service)
2. The WSE soap extension is configured for the service. (It has to be
configured in the web.config file)
3. The service has a PolicyAttribute that points to the
UsernameOverTransport assertion

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

>I am trying to implement the UsernameOverTransport Assertion in WSE 3.0. I
> will be authenticating against a .NET 2.0 Membership system, so I have
[quoted text clipped - 14 lines]
> Any thoughts on why the service does not recognize the UsernameToken? or
> where to look?

Reply to this Message

WSE 3.0 - UsernameOverTransport Assertion - SOAP Header Exception

Free Magazines