Re: Integrated Authentication Fails, Basic Authentication works
From: Ken Schaefer (kenREMOVE_at_THISadOpenStatic.com)
Date: Thu, 7 Aug 2003 13:53:16 +1000
With Integrated Authencation, the web server *never* has the user's
password, so it can't authenticate to the remote machine on the user's
behalf. When you use Basic authentication, then the user's username and
password are both sent in clear-text to the webserver, so it can then
"impersonate" the user account to the remote file server, allowing you to
manipulate resources remote to the webserver.
For this reason, it is recommended to use SSL in combination with Basic
"Kevin Jackson" <email@example.com> wrote in message
: I'm seeing sort of the same situation myself. In my case, I'm trying to
: copy a file to a share point on another box and it doesn't appear my user
: context is getting set correctly with Integrated Authentication and
: therefore the ASP page doesn't have sufficient rights to copy the file.
: I can get it to work with basic but not with authenticated if I'm copying
: off box.
: Very strange...
: "Dan" <firstname.lastname@example.org> wrote in message
: > I was wondering if anyone has seen this before? We have a Win 2k
: > server (sp3) w/ IIS v5. The server is on an Active Directory with
: > valid domain accounts. When we set the directory security to
: > Integrated we cannot logon w/ domain users. The NTFS security is wide
: > open on the directory and the users are administrators. If we create
: > a local acount, we can logon no problem. If we switch to Basic Auth
: > we can logon no problem w/ the domain accounts.
: > As soon as we enable windows auth, no go? Not sure if there is a
: > policy setting, hack, patch or what for this?
: > Any help would be appreciated.