|
I had
similar problem with the .NET client because in by back-end server (JBoss, web
service implemented as an EJB) I enabled a default identity to be used for
unauthenticated user.
To
make it short, it seems that the .NET client will not send any user/password in
the HTTP header (Authentication HTTP header) until it receives a request
for authentication. Your server must deny the first request sent from the .NET
client. When doing that, it is supposed, in the deny response, to send a
WWW-Authenticate header to the client, which will try the request again and
that time with the Authentication header (which will contain
user/password).
Use
the tcpmon of Axis to see what is going on at the HTTP level. As long as your
server will not send back any WWW-Authenticate header, the .NET client will not
send the Authentication header (or at least that is the behavior I
observed).
Thomas
-----Original Message----- From: Vidyanand Murunikkara [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 2:42 AM To: [EMAIL PROTECTED] Subject: RE: Calling a secure Axis web service with .net client
|
Title: RE: Calling a secure Axis web service with .net client
- Calling a secure Axis web service with .net client Vidyanand Murunikkara
- RE: Calling a secure Axis web service with .net... thomas . cherel
- RE: Calling a secure Axis web service with .net... Vidyanand Murunikkara
- thomas . cherel
