Re: Action Missing

It is not just a namespace change. The implemented addressing specifications
are different.
--
Thank you.

Regards,
William Tay
http://www.softwaremaker.net/blog
=========================================

"Oldman" <Oldman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9CFD31C8-1468-4975-9AB1-DDA494E7BF16@xxxxxxxxxxxxxxxx
Let me rephrase this question just a bit.
The fact that the WSE 2.0 uses a different namepsace for the wsa elements
seems to cause this problem. Is there a way to get the WSE 2.0 client to
use
the newer namepsace?

Thanks again,

Chris

"Oldman" wrote:

I have a web service secured using WSE 3.0. I have a client trying to
communicate to the web service and they are using WSE 2.0 SP2.
We are getting the following error:

Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for
ultimate
recipient is required but not present in the message.

Here is the beginning of the web request that is produced from WSE 2.0
SP2:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing";

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd"

xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
y-utility-1.0.xsd">
<soap:Header>
<wsa:Action

wsu:Id="Id-8e3d449c-436a-4568-8def-07eea3196e4c">http://convergencedata.net/
CreateItems</wsa:Action>
<wsa:MessageID

wsu:Id="Id-c6e0068f-6cf7-4428-96fd-4475e5449f28">uuid:bddc46ec-1787-4c18-a81
1-2593fc87ad07</wsa:MessageID>
<wsa:ReplyTo wsu:Id="Id-1a746231-bf96-483d-88a9-45f208c8c7db">


<wsa:Address>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous
</wsa:Address>
</wsa:ReplyTo>

Notice the action tag is specified. However, notice that the
wsa:Address
tag contains a different URL than
http://schemas.xmlsoap.org/ws/2004/08/addressing.
This and the fact that when using a WSE 3.0 client the wse:ID attributes
aren't used are the only differences in the soap messages.

Is that URL causing the problem and if it is how do I get it to use the
newer 08/2004 schema?


.

Relevant Pages

  • Re: How to call Web Service Securely
    ... Maybe I am complicating WSE too much - can you point me to a simple ... you could provide a logon screen in the client app and create a NetworkCredential ... tokens - but that is tied to .NET 2.0 ... make a web method via dialup to my IIS Web Service. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • WSE3 web farm problem: "Key not valid for use in specified state"
    ... I have a web service in ASP.NET 2.0 and WSE 3.0. ... server1, and the actual request went to server2, like the following ... Client output: RST ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Web Services, Security, X.509
    ... We have a smart client application which consumes an internet-facing ... (At this time the web service and the client use ... WSE 3.0 and it is working ... Finally, if a X.509 certificate is required, which certificate is the ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • had to elevate ASPNET account user rights assignment
    ... I have a client running in our office and asp.net web service ... I finally got the wse 2.0 enabled asp.net web service ... authenticate my username and password as cleartext? ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Problem invoking WSE 2.0 enabled WebService
    ... Yes I mean secure web service implemented with WSE. ... enabled web service by manually creating the security header from the ... you can not consume it from a client application that ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
Loading