Re: IIS Web Service 401 Error with Integrated Windows Authenticati

From: DownUnder (DownUnder_at_discussions.microsoft.com)
Date: 08/19/04


Date: Wed, 18 Aug 2004 16:55:01 -0700


I think I now know the reason why I was led to think that the credentials
are passed automatically:

It is the "impersonation" setting that I was using (on the server side). I
thought when that setting was used in the web.config file, the credentials
from the client were passed automatically somehow. I was wrong...they need to
be set on the client explicitly as the following KB article states.

"http://support.microsoft.com/default.aspx?scid=kb;EN-US;811318"

"DownUnder" wrote:

>
> Thanks for the reply, Michael. The problem is not definitely related to the
> webserver name since the problem happens when the authentication type is
> changed (everything else being the same).
>
> My internet search today has given me some clue. It looks like I need to set
> the "Credentials" for the service programmatically to "DefaultCredentials" in
> the client code.
>
> I donot know much about that topic and I am not sure why this is not done
> automatically. I am also surprised to learn that it needs to be done in the
> client programmatically. I have tried it and it seems to solve the problem I
> had. However, I need to find out and learn more about the topic.
>
> Regards,
>
> DownUnder.
>
>
>
>
>
> "Raterus" wrote:
>
> > Are you using a fully-qualified domain name for the webserver? If so you might want to check out this article about setting the SPN's
> >
> > http://support.microsoft.com/default.aspx?kbid=294382
> >
> > --Michael
> >
> > "DownUnder" <DownUnder@discussions.microsoft.com> wrote in message news:F66965B4-1B93-4264-90F2-C90CE6B62467@microsoft.com...
> > >
> > > Hi,
> > >
> > > I have 401 Error when I try to invoke an ASP Web Service through a client if
> > > Windows Authentication is used.
> > >
> > > To identify the reason, I built a simple "Hellow World" Web Service that I
> > > can successfully invoke using IE (regardless of the authentication type
> > > configured in IIS).
> > >
> > > I can invoke the same Web Service by another client successfully if the
> > > authentication type is Anonymous (regardless of the actual user who it runs
> > > under).
> > >
> > > However, if the Integrated Windows Authentication is ticked, invoking the
> > > service fails (even for the users configured for Anonymous access).
> > >
> > > I tried it on XP Professional and IIS 6. (However, I have the same result on
> > > Win2K3.)
> > >
> > > Help is very much appreciated.
> > >
> > > DownUnder.
> > >
> >



Relevant Pages

  • Re: BASIC authentication Issues with IE - Part II - Solved but WHY?
    ... it does not know the difference between a request from IE or from ... some other HTTP client. ... Some other authentication schemes are more ... IIS can sometimes remember the token for a particular set of credentials so ...
    (microsoft.public.inetserver.iis.security)
  • Re: Authentication woes
    ... I can not really understand how the client should connect to the DC when they are at work with the 192.x.x.x ip when the server is in 10.x.x.x network. ... If i read the output for the client it is member of domainb.internal and not member of domain.com like the DC, ... If the user logon with cached credentials, ...
    (microsoft.public.windows.server.active_directory)
  • Re: CM & SW
    ... when a user is logged in or no user logged in, and the credentials (use user ... could successfully install the package "whether or not a user is logged in", ... testing, showing me when a new policy or updated policy has been retrieved, ... Zander's SMS Client Center. ...
    (microsoft.public.sms.swdist)
  • Re: CM & SW
    ... when a user is logged in or no user logged in, and the credentials (use user ... install using your DOMAIN\user credentials, ... testing, showing me when a new policy or updated policy has been retrieved, ... Zander's SMS Client Center. ...
    (microsoft.public.sms.swdist)
  • Re: Terminal Services Security Issue with Cached Credentials
    ... I tried the setting "Allways prompt client for password upon connect" ... on a server and then tried connecting to it using cached credentials. ... What version of the Terminal Services client are you using? ... "Always prompt client for password upon connection" ...
    (microsoft.public.windows.server.security)

Quantcast