Re: Unrecogniszed SOAPAction?

Setting the attribute establishSecurityContex="false" seemed to do the trick.
What is that attribute?

Thank you.

Kevin

"Pablo Cibraro [MVP]" wrote:

Hi Kevin,

The first error happens when the security conversation is enabled on the
client side only (The service does not expect the SCT action).
Make sure to have the attribute establishSecurityContext="false" on both
sides, the client and the service.

The second error is a generic one, you will have to take a look to the
eventlog or the WSE trace file to find out the real error.

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

"Kevin Burton" <KevinBurton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6D8FC4FF-3074-4378-AF9D-A545A371A93A@xxxxxxxxxxxxxxxx
After modifying the configuration file some I am now getting:

Security requirements are not satisfied because the security header is not
present in the incoming message

I am guessing that this is a problem with the client that is not sending
or
setting the security header. Any ideas on how I can trace this further?

Thanks again.

Kevin


"Kevin Burton" wrote:

I am trying to modify some of the sample WSE 3.0 security samples and I
am
getting:

System.Web.Services.Protocols.SoapException: Server did not recognize the
value of HTTP Header SOAPAction:
http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT.
at
System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest()
at
System.Web.Services.Protocols.SoapServerProtocol.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&
abortProcessing)

This is a simple HelloWorld sample I am not sure where the SoapAction is
coming from. Any ideas?

Thank you.

Kevin Burton



.

Relevant Pages
Loading