Integrated Windows Authentication (IWA)[1]is a term associated withMicrosoft products that refers to theSPNEGO,Kerberos, andNTLMSSP authentication protocols with respect toSSPI functionality introduced with MicrosoftWindows 2000 and included with laterWindows NT-based operating systems. The term is used more commonly for the automatically authenticated connections between MicrosoftInternet Information Services,Internet Explorer, and otherActive Directory aware applications.
IWA is also known by several names likeHTTP Negotiate authentication,NT Authentication,[2]NTLM Authentication,[3]Domain authentication,[4]Windows Integrated Authentication,[5]Windows NT Challenge/Response authentication,[6] or simplyWindows Authentication.
Integrated Windows Authentication uses the security features of Windows clients and servers. UnlikeBasic Authentication orDigest Authentication, initially, it does not prompt users for a user name and password. The current Windows user information on the client computer is supplied by the web browser through a cryptographic exchange involving hashing with the Web server. If the authentication exchange initially fails to identify the user, the web browser will prompt the user for a Windows user account user name and password.
Integrated Windows Authentication itself is not a standard or an authentication protocol. When IWA is selected as an option of a program (e.g. within theDirectory Security tab of theIIS site properties dialog)[7] this implies that underlying security mechanisms should be used in a preferential order. If theKerberos provider is functional and aKerberos ticket can be obtained for the target, and any associated settings permit Kerberos authentication to occur (e.g. Intranet sites settings inInternet Explorer), the Kerberos 5 protocol will be attempted. OtherwiseNTLMSSP authentication is attempted. Similarly, if Kerberos authentication is attempted, yet it fails, then NTLMSSP is attempted. IWA usesSPNEGO to allow initiators and acceptors to negotiate either Kerberos or NTLMSSP. Third party utilities have extended the Integrated Windows Authentication paradigm to UNIX, Linux and Mac systems.
Integrated Windows Authentication works with most modern web browsers,[8] but does not work over some HTTPproxy servers.[7] Therefore, it is best for use inintranets where all the clients are within a singledomain. It may work with other web browsers if they have been configured to pass the user's logon credentials to the server that is requesting authentication. Where a proxy itself requires NTLM authentication, some applications like Java may not work because the protocol is not described in RFC-2069 for proxy authentication.
iOS natively supports Kerberos viaKerberos Single Sign-on extension. Configuring the extension enables Safari and Edge to use Kerberos.
Android hasSPNEGO support in Chrome which is adding Kerberos support with a solution likeHypergate Authenticator.
This advisory addresses [...] Integrated Windows Authentication (IWA) [...]
[...] Windows NT supported two kinds of challenge/response authentication: [...] LanManager (LM) challenge/response [...] Windows NT challenge/response (also known as NTLM challenge/response) [...] LM authentication is not as strong as Windows NT authentication [...]
Integrated Windows authentication (formerly known as NTLM authentication [...]) [...]
When the NTLM protocol is used, a resource server must [...] Contact a domain authentication service
Windows Integrated authentication, Windows NT Challenge/Response (NTCR), and Windows NT LAN Manager (NTLM) are the same and are used synonymously throughout this article.
Integrated Windows authentication (formerly known as [...] Windows NT Challenge/Response authentication) [...]