Re: .NET WS client connecting to Axis WS - credentials problem



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" <DavidR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE1C9AD4-A637-4EEE-A012-AE537091AE31@xxxxxxxxxxxxxxxx
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.Credentials = new System.Net.NetworkCredential("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



.



Relevant Pages

  • Re: Authentication between sites
    ... > credentials into the Http header, ensuring you have the name-value pair ... User or Username) nor the password, ... > Network monitor is part of the Win2000/2003 Server install but you I am ... > authentication, so everytime they go to view that report, it asks them to ...
    (microsoft.public.dotnet.security)
  • Re: Alternative to username:password@domain
    ... sure of the syntax for adding a header to a WinInet web request, ... The basic authentication header is called "authorization" and looks like ... WinInet may also have built-in support for providing credentials and passing ... > Dear Joe, ...
    (microsoft.public.dotnet.security)
  • OTP with SOAP messages and swing client
    ... At the moment we use a dodgy WS-Security header with username and base64 encoded password in the soap header. ... User requests OTP via some mechanism where they provide username/password, server creates a nonce and a secret and sends it to their pre-configured mobile number via SMS ...
    (Security-Basics)
  • Re: Basic Authentication problem
    ... I've written my first attempt at basic authentication and it doesn't ... don't know if it makes a difference - but I normally put the authorization header just before the content type. ... If you're running Firefox, you can get the Live HTTP Headers extension for it. ...
    (comp.lang.php)
  • How to extract the NT username from NTLM message?
    ... NT username from the "Authirization:" header that is sent from the ... I configured IIS to use Windows Authentication and disabled ... anonymous access in order to force the client send its credentials. ...
    (microsoft.public.dotnet.framework)