.NET WS client connecting to Axis WS - credentials problem

[David R]

I am writing a .NET web services client that is calling an Axis web service.
I have two questions.

1. The following code should set the authentication; when I call a method
on the web service, the call fails with "bad username/password".

// wrWorkReq is the name of the service
wrWorkReq.Crede ntials = new System.Net.Netw orkCredential(" adolph.ramirez" ,
"xxx");

A developer managing the Axis side says that the server is receiving a blank
username and password, and not the populated fields they should be. Any idea
what I am doing wrong?

2. I could save time if I could debug the HTTP headers that are being sent
out. I am using VS 2005. Any suggestions on the best way to do this?

Thanks,

David

[Pablo Cibraro]

Hi David,

That property sets the credentials for the transport (In case you are using
Http, it sets the credentials when Basic authentication or Windows
authentication is being used). In other words, as you said, adds a http
header with the credentials.
Maybe the service is being protected with the WS-Security, and they are
expecting a security header in the SOAP message. (The security header
contains a Usernametoken with user and password). In this case, you need to
add a SOAP-Header and not a Http Header.

You should first ask to the web service team whether they are using
WS-Security or not.

Regards,
Pablo Cibraro.
"David R" <Da****@discuss ions.microsoft. comwrote in message
news:CE******** *************** ***********@mic rosoft.com...

>I am writing a .NET web services client that is calling an Axis web
service.
I have two questions.

1. The following code should set the authentication; when I call a method
on the web service, the call fails with "bad username/password".

// wrWorkReq is the name of the service
wrWorkReq.Crede ntials = new System.Net.Netw orkCredential(" adolph.ramirez" ,
"xxx");

A developer managing the Axis side says that the server is receiving a
blank
username and password, and not the populated fields they should be. Any
idea
what I am doing wrong?

2. I could save time if I could debug the HTTP headers that are being sent
out. I am using VS 2005. Any suggestions on the best way to do this?

Thanks,

David

[David R]

Thanks for the response. Basic authentication is being used, and since the
Axis developer said that the blank username was appearing in the http header,
then ws-security is not being used.

If I could view the header information of the request coming from my client
application (debugging on the client, not the server), using VS2005 or
something else, then I might be able to resolve the problem myself.

Thanks,

David
"Pablo Cibraro" wrote:

Hi David,

That property sets the credentials for the transport (In case you are using
Http, it sets the credentials when Basic authentication or Windows
authentication is being used). In other words, as you said, adds a http
header with the credentials.
Maybe the service is being protected with the WS-Security, and they are
expecting a security header in the SOAP message. (The security header
contains a Usernametoken with user and password). In this case, you need to
add a SOAP-Header and not a Http Header.

You should first ask to the web service team whether they are using
WS-Security or not.

Regards,
Pablo Cibraro.
"David R" <Da****@discuss ions.microsoft. comwrote in message
news:CE******** *************** ***********@mic rosoft.com...

I am writing a .NET web services client that is calling an Axis web
service.
I have two questions.

1. The following code should set the authentication; when I call a method
on the web service, the call fails with "bad username/password".

// wrWorkReq is the name of the service
wrWorkReq.Crede ntials = new System.Net.Netw orkCredential(" adolph.ramirez" ,
"xxx");

A developer managing the Axis side says that the server is receiving a
blank
username and password, and not the populated fields they should be. Any
idea
what I am doing wrong?

2. I could save time if I could debug the HTTP headers that are being sent
out. I am using VS 2005. Any suggestions on the best way to do this?

Thanks,

David