WCF (.NET 4.0) + IIS 7 + Windows 身份验证错误 - "service require Windows Authentication but it is not enabled for the IIS application "

Question

我们有一个简单的 WCF(在 .NET 4.0 上)服务，它使用 Windows 身份验证，并且在 IIS 7 身份验证功能上启用了相同的功能。这适用于两台服务器上的相同设置和相同配置，但其中一台服务器返回错误 此服务的安全设置需要 Windows 身份验证，但未为托管此服务的 IIS 应用程序启用。 我在网上检查了所有可能的内容，并尝试了所有选项，例如禁用其他身份验证机制等。似乎没有任何效果。谁能指出可能是什么问题。同样，两台服务器上的相同设置在第三台服务器上运行良好，但出现问题。

<?xml version="1.0"?>
<configuration>
  <appSettings>
    <add key="ABCDbConnection" value="Data Source=xxx; Initial Catalog=sss;Integrated Security=True"/>
    <add key="MetadataDbConnection" value="Data Source=xxx; Initial Catalog=sss;Integrated Security=True"/>
    <add key="UsageEnabled" value="True"/>
  </appSettings>
  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>
    <protocolMapping>
      <add scheme="http" binding="basicHttpBinding" bindingConfiguration="WindowsBasicHttpBinding"/>
    </protocolMapping>
    <behaviors>
<serviceBehaviors>
    <behavior>
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="true"/>
          <dataContractSerializer maxItemsInObjectGraph="6553600"/>
    </behavior>
</serviceBehaviors>
</behaviors>
<bindings>
  <basicHttpBinding>
    <binding name="WindowsBasicHttpBinding">
      <security mode="TransportCredentialOnly">
            <transport clientCredentialType="Windows"/>
          </security>
        </binding>
      </basicHttpBinding>
    </bindings>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

Answer 1

此线程中的任何解决方案是否有效？

http://social.msdn.microsoft.com/Forums/en/wcf/thread/021babc6-2009-4ed9-81f4-ac48cc300c94

从这里blog post , 它提到了这个 KB article .

If this error is returned and Windows Authentication has been enabled in IIS, it means there is an issue with the supported network authentication schemes for the website that the web service is installed under. The most likely cause is that it is configured for NTLM only. We want to specify NTLM and Negotiate.