| Vince C. 2004-04-29, 7:34 am |
| Hi.
I'm facing a problem I don't understand. I have written a 3 tier application
in classical ASP. Two tiers are IIS 5.0 with classical ASP. The first tier
acts like a proxy to access the second one. The proxy tier sends SOAP
requests to the SOAP server tier. The server tier uses low-level API to
process calls while the proxy tier uses high level API
(MSSoap.SoapClient30).
The third tier is a web browser (Internet Explorer). Data exchanges between
the two server tiers must be authenticated. Authentication occurs when a
user browses the proxy tier using Internet Explorer 6.
Both server tiers run on distinct W2K machines, on which platforms can be
different but each must be either Professional or Server versions of Windows
2000. Both machines are registered in the same W2K domain (Active Directory
enabled). If the platform is a W2K Server, it is standalone, not a domain
controller.
My problem occurs as I run SOAP access tests against the server tier when.
I'm using XML Spy to run my tests. When I attempt to send requests to the
Soap server, XML Spy prompts for credentials as expected. If I provide
credentials for a domain user, authentication fails and the browser receives
a "401 Forbidden" HTTP status. Recall that both the server and the
workstation on which I'm running tests are in the same W2K domain.
OTOH if I provide credentials for a user account that is local to the Soap
server, authentication succeeds and I receive an expected Soap message in
return.
What I don't understand is the same test worked a couple of weeks ago. I
recall seeing posts about problems with authentication such as this one.
Is it a known issue? Have I missed something? I've tried to run the same
tests on several machines and I always get the same error.
Can someone help?
Thanks in advance.
Vince C.
|