Hi,
Is it possible to consume a WSE 3.0 enabled webservice in a console application which is developed in .Net 1.1 framework
I tried to call this web service from console application, but is asking for a policy to be set. since my console application is developed under .NET 1.1 framework, how can I set the policy.
What I understood from WSE 3.0 concept is, In order to consume WSE 3.0 enabled webservice, the consumer application should have WSE 3.0.
If am right, Is it possible to build a WSE 3.0 enabled webservice without any dependency on the consumer
Please, give me some suggestions.
Thanks in advance.
How to consume WSE 3.0 enabled webservice
Brian_t
Thanks for the solution.
I am facing one more problem. I have a web service which is WSE 3.0 enabled with customauthentication.
I am able to access this web service from ASP.NET web application with secure SOAP header.
and also I am able to access this web service from classic ASP page without any secure soap header. So is it possible to deny the access of web service from classic ASP page without secure header in the web service
Please advice me some solution.
Hansraj.
Mike Droney MSFT
>>What I understood from WSE 3.0 concept is, In order to consume WSE 3.0 enabled webservice, the consumer application should have WSE 3.0.
Yes. The client needs to know the specifications supported by the web Service Endpoint, so the client needs to be WSE 3.0 enabled with the same specifications. WSE 3.0 was designed to align with the WCF specifications to achieve interoperability. For example the WS-Addressing specification which in WSE 3.0 is aligned with a 2004/08 version, is different from WSE 2.0
You can work around some specifications differences. For example see here for the WS-Addressing. For security, given that WSE 3.0 supports the newly approved WS-Security 1.1. the only scenarios that could work from WSE 2.0 to WSE 3.0 are UsernameOverTransport and MutualCertificate10.
The recommendation is to host both WSE 2.0 and WSE 3.0 on the same machine in order for different clients to talk to your commonly (factored out) business logic with different endpoints. WSE simply provides the security and parsing of the WS-* specifications that you are using for that client. See here for more details on the WSE 2.0 and WSE 3.0 support.
Thanks. Mark
Bespi
I am not sure that I understand. You have to send an XML SOAP message with the correct security credentials, irrespective of where the message originates from.
I take it that you are loading ASP pages, but these pages are accessing the SOAP services, not that you are calling the SOAP services directly from the Web client.
Can you provide some more detail around your setup and scenario
Thanks, Mark