主页 / server / 问题 / 114352
In Process
Asked: 2010-02-19 10:20:55 +0800 CST

IIS 7 身份验证：某些用户无法进行身份验证，而几乎所有其他用户都可以

  • 772

我正在使用 IIS 7 Digest 身份验证来控制对包含文件的某个目录的访问。用户通过我们网络内部和外部的部门网站访问文件。我已经在目录上设置了 NTFS 权限，以允许某个 AD 组查看文件。当我单击网站上其中一个文件的链接时，系统会提示我输入用户名和密码。对于大多数用户来说，一切正常，但对于其中一些用户，它会提示输入密码 3 次，然后得到：

401 - 未经授权：由于凭据无效，访问被拒绝。

但是该组中的其他用户可以毫无问题地进入。如果我将它切换到 Windows 身份验证，那么麻烦的用户可以正常登录。那个目录也是共享的，不能通过网站登录的用户可以浏览到共享并查看里面的文件，所以我知道权限是ok的。

这是我尝试下载文件的 IIS 日志部分（/assets/files/secure/WWGNL.pdf）：

2010-02-19 19:47:20 xxx.xxx.xxx.xxx GET /assets/images/bullet.gif - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 200 0 0 218
2010-02-19 19:47:20 xxx.xxx.xxx.xxx GET /assets/images/bgOFF.gif - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 200 0 0 218
2010-02-19 19:47:21 xxx.xxx.xxx.xxx GET /assets/files/secure/WWGNL.pdf - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 401 2 5 0
2010-02-19 19:47:36 xxx.xxx.xxx.xxx GET /assets/files/secure/WWGNL.pdf - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 401 1 2148074252 0
2010-02-19 19:47:43 xxx.xxx.xxx.xxx GET /assets/files/secure/WWGNL.pdf - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 401 1 2148074252 15
2010-02-19 19:47:46 xxx.xxx.xxx.xxx GET /manager/media/script/_session.gif 0.19665693119168282 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 200 0 0 203
2010-02-19 19:47:46 xxx.xxx.xxx.xxx POST /manager/index.php - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 200 0 0 296
2010-02-19 19:47:56 xxx.xxx.xxx.xxx GET /assets/files/secure/WWGNL.pdf - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 401 1 2148074252 15
2010-02-19 19:47:59 xxx.xxx.xxx.xxx GET /favicon.ico - 80 - 10.5.16.138 Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+en-US)+AppleWebKit/532.5+(KHTML,+like+Gecko)+Chrome/4.0.249.89+Safari/532.5 404 0 2 0

这是安全日志中的失败登录尝试：

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          2/19/2010 11:47:43 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      WEB4.net.domain.org
Description:
An account failed to log on.

Subject:
    Security ID:        NULL SID
    Account Name:       -
    Account Domain:     -
    Logon ID:       0x0

Logon Type:         3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:       jim.lastname
    Account Domain:     net.domain.org

Failure Information:
    Failure Reason:     Unknown user name or bad password.
    Status:         0xc000006d
    Sub Status:     0xc000006a

Process Information:
    Caller Process ID:  0x0
    Caller Process Name:    -

Network Information:
    Workstation Name:   -
    Source Network Address: 10.5.16.138
    Source Port:        50065

Detailed Authentication Information:
    Logon Process:      WDIGEST
    Authentication Package: WDigest
    Transited Services: -
    Package Name (NTLM only):   -
    Key Length:     0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2010-02-19T19:47:43.890Z" />
    <EventRecordID>2276316</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="692" />
    <Channel>Security</Channel>
    <Computer>WEB4.net.domain.org</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">jim.lastname</Data>
    <Data Name="TargetDomainName">net.domain.org</Data>
    <Data Name="Status">0xc000006d</Data>
    <Data Name="FailureReason">%%2313</Data>
    <Data Name="SubStatus">0xc000006a</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">WDIGEST</Data>
    <Data Name="AuthenticationPackageName">WDigest</Data>
    <Data Name="WorkstationName">-</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">10.5.16.138</Data>
    <Data Name="IpPort">50065</Data>
  </EventData>
</Event>
active-directory authentication iis-7 digest

2 个回答

  1. 可能不是您想要的答案，但是：不要使用 Digest。我发现它在浏览器、浏览器版本、服务器版本和 Windows 版本中无法始终如一地工作。（我只是稍微夸大了一点）。

    它也可能需要也可能不需要可逆加密，具体取决于使用的版本（Advanced Digest vs Digest vs IIS SubAuthentication）。

    让其中一位有问题的用户重设密码。如果问题消失了，让其他人也这样做。

    • 1

  2. 您的所有用户都在同一个域中吗？所有用户都在同一个网络上吗？文件服务器或文件共享是否与 Web 服务器在同一个域中？

    问题是否与用户位置一致？例如，在内部访问网站时它可以工作，但在外部访问它时却不行？

    我还建议您使用 Firefox 等替代浏览器进行测试。系统会提示您输入用户名和密码，但我已经看到 FF 将进行身份验证而 IE 不会进行身份验证。由于 IE 客户端设置（例如安全区域和 IE 设置），我在 IE 身份验证方面遇到了很多问题。

    戴夫

    • 0

相关问题