Connecting to a WSE 3.0 security enabled web service with .Net 1.1

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • =?Utf-8?B?Q2hhaXRhbnlh?=

    #1

    Connecting to a WSE 3.0 security enabled web service with .Net 1.1

    I have created a WSE 3.0 security enabled web service using a custom username
    token manager. Everything is working properly when I consume this web
    service with a WSE enabled client application. I am able to execute the web
    methods and return the data as needed.

    However, I also need to be able to provide information on how to connect to
    this service with a .Net 1.1 application. I do know that WSE 3.0 doesn't
    support .Net 1.1, but it should still be able to connect and run the web
    methods. This is where I am stuck at. I am unsure about how I need to
    modify the soap header to be able to provide the needed credentials that as
    used by the custom username token manager.

    I have tried, without WSE 3.0 in the project, adding the credentials to the
    web service proxy. That didn't work. It still produces the below error:

    Microsoft.Web.S ervices3.Securi ty.SecurityFaul t: Header
    http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate
    recipient is required but not present in the message.

    So does anyone have any type of examples on how to connect to the WSE 3.0
    web service WITHOUT using WSE on the client side?

    Any pointer in the right direction would be very much appreciated.

Working...