Criteria for IE to Negotiate Kerberos and Not NTLMSSP



Hi,

I have a web service product that runs on UNIX and does GSSAPI
and requires IE to negotiate Kerberos using Integrated Windows
Authentication. The log on the customer's site is showing that IE is
only asking for NTLMSSP. We're having trouble tracking down why.

I know of the usual reasons for not negotiating Kerberos (or Integrated
Windows Authentication in general) but I would like to create a
comprehensive list in anticipation of creating a wscript utility to
check a workstation for compatibility with my product. Can anyone add
to (or eliminate from) the list below? Are there any other configuration
options or perhaps registry settings somewhere?

Thanks,
Mike

The following is a list of criteria for Internet Explorer to negotiate
Kerberos with a web service (e.g. IIS):

1) The client workstation must be running Windows 2000, Windows XP,
or Windows 2003. Windows NT 4 and Windows 98 or previous do not support
Integrated Windows Authentication.

2) The client workstation must be joined to the target Windows
domain. Check Control Panel > System > Computer Name tab > Change ... and
make sure the client is a member of the correct domain and not just
a workgroup.

[Q: Is it important that the domain name of the client and Kerberos
realm share the same suffix?]

3) The user logged into the workstation using IE must be logged into
the domain. Check Ctrl+Alt+Del and look at the "You are logged on as"
dialog. The Windows domain shown must be the target domain and not the
local machine name. If the user is not logged into the domain, logoff,
select the domain in the drop down labeled "Log on to", and enter the
user's domain credentials (assuming they have domain credentials).

4) Integrated Windows Authentication must be enabled. Check Tools >
Internet Options > Advanced > scroll all the way to the bottom and
make sure "Enable Integrated Windows Authentication (requires restart)"
is checked.

5) Automatic logon must be enabled [1]. Check Tools > Internet Options >
Securty > Custom Level > scroll all the way to the bottom and make sure
"Automatic logon with current username and password" is selected.

6) The target website must be listed in the IntrAnet zone [1]. Check
Tools > Internet Options > Security > Local Intranet and make sure the
target domain is listed there. For example, if your domain is foo.net
add http://*.foo.net and https://*.foo.net. Or you may explicitly add
a specific site (e.g. http://www.foo.net).

[1] Actually this is may not be necessary if the site is in the Trusted
sites list (under Tools > Internet Options > Security).

.



Relevant Pages

  • Re: Integrated Windows Authentication, Change IEs Reaction to a 401.3
    ... monitor the Windows event logs for repeated failed logon attempts. ... > to display a login prompt because it was an invitation for hackers to ... >> Using Integrated Windows Authentication on a Windows 2000 Server ...
    (microsoft.public.inetserver.iis.security)
  • Re: Windows Integrated and the domain name
    ... Windows domain related issue. ... As for IIS server side, ... for a direct integrated windows authentication ... Microsoft Online Community Support ...
    (microsoft.public.inetserver.iis.security)
  • Re: Using IIS w/ASP .NET 2.0 Web Application Projects
    ... if you enable Windows Integrated Authentication, ... See my previous post for more details regarding use of Windows Authentication with ASP.NET. ... at least within non-ASP.NET IIS applications. ... Integrated Windows Authentication overrides the Anonymous authentication default. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Using IIS w/ASP .NET 2.0 Web Application Projects
    ... If you select Windows Integrated Authentication, anonymous users won't be able to login. ... ASP.NET has a *separate* authentication configuration which IIS doesn't interfere with. ... Integrated Windows Authentication overrides the Anonymous authentication default. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: NT integrated is prompting for login????
    ... | I have a number of IIS 5 boxes set up running on windows 2000 servers. ... | anonymouse access box and left the integrated Windows authentication ... 198116 Authentication Options and Limitations Using Proxy Server 2.0 ...
    (microsoft.public.inetserver.iis.security)