NTLM Over HTTP Protocol Specification

[MS-NTHT]:
NTLM Over HTTP Protocol Specification
Intellectual Property Rights Notice for Open Specifications Documentation
 Technical Documentation. Microsoft publishes Open Specifications documentation for

protocols, file formats, languages, standards as well as overviews of the interaction among each
of these technologies.
 Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other

terms that are contained in the terms of use for the Microsoft website that hosts this
documentation, you may make copies of it in order to develop implementations of the
technologies described in the Open Specifications and may distribute portions of it in your
implementations using these technologies or your documentation as necessary to properly
document the implementation. You may also distribute in your implementation, with or without
modification, any schema, IDL’s, or code samples that are included in the documentation. This
permission also applies to any documents that are referenced in the Open Specifications.
 No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
 Patents. Microsoft has patents that may cover your implementations of the technologies
described in the Open Specifications. Neither this notice nor Microsoft's delivery of the
documentation grants any licenses under those or any other Microsoft patents. However, a given
Open Specification may be covered by Microsoft's Open Specification Promise (available here:
http://www.microsoft.com/interop/osp) or the Community Promise (available here:
http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if
the technologies described in the Open Specifications are not covered by the Open Specifications
Promise or Community Promise, as applicable, patent licenses are available by contacting
[email protected].
 Trademarks. The names of companies and products contained in this documentation may be
covered by trademarks or similar intellectual property rights . This notice does not grant any
licenses under those rights.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights
other than specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications do not require the use of Microsoft programming tools or
programming environments in order for you to develop an implementation. If you have access to
Microsoft programming tools and environments you are free to take advantage of them. Certain
Open Specifications are intended for use in conjunction with publicly available standard
specifications and network programming art, and assumes that the reader either is familiar with the
aforementioned material or has immediate access to it.
1 / 21
[MS-NTHT] — v20090924
Copyright © 2009 Microsoft Corporation.
Release: Thursday, September 24, 2009

Revision Summary
Revision Revision
Date History Class Comments
03/14/2007 1.0 Version 1.0 release
06/08/2007 1.2.1 Editorial Revised and edited the technical content.
10/26/2007 2.0 Major Converted document to unified format and updated the
technical content.
06/20/2008 3.0 Major Updated and revised the technical content.
07/25/2008 3.1 Minor Updated the technical content.
12/05/2008 4.0 Major Updated and revised the technical content.
2 / 21
[MS-NTHT] — v20090924

Contents
1 Introduction ..................................................................................................................... 5
1.1 Glossary.........................................................................................................................5
1.2 References .....................................................................................................................5
1.2.1 Normative References ..............................................................................................5
1.2.2 Informative References ............................................................................................6
1.3 Protocol Overview (Synopsis) .........................................................................................6
1.4 Relationship to Other Protocols .......................................................................................6
1.5 Prerequisites/Preconditions.............................................................................................6
1.6 Applicability Statement...................................................................................................6
1.7 Versioning and Capability Negotia tion .............................................................................6
1.8 Vendor-Extensible Fields ................................................................................................6
1.9 Standards Assignments ..................................................................................................7
2 Messages .......................................................................................................................... 8
2.1 Transport .......................................................................................................................8
2.2 Message Syntax .............................................................................................................8
2.2.1 WWW -Authenticate Response Header.......................................................................8
2.2.2 Authorization Request Header ..................................................................................8
2.2.3 Proxy-Authenticate Response Header .......................................................................9
2.2.4 Proxy-Authorization Request Header.........................................................................9
3 Protocol Details.............................................................................................................. 11
3.1 Common Details........................................................................................................... 11
3.1.1 Abstract Data Model ............................................................................................... 11
3.1.2 Timers ................................................................................................................... 11
3.1.3 Initialization ........................................................................................................... 11
3.1.4 Higher-Layer Triggered Events ............................................................................... 11
3.1.5 Message Processing Events and Sequencing Rules .................................................. 11
3.1.5.1 Unexpected Messages ...................................................................................... 11
3.1.6 Timer Events.......................................................................................................... 11
3.1.7 Other Local Events ................................................................................................. 11
3.2 Server Details .............................................................................................................. 11
3.2.2 Timers ................................................................................................................... 12
3.2.3 Initialization ........................................................................................................... 12
3.2.6 Timer Events.......................................................................................................... 12
3.3 Client Details................................................................................................................ 12
3.3.2 Timers ................................................................................................................... 12
3.3.3 Initialization ........................................................................................................... 12
3.3.6 Timer Events.......................................................................................................... 13
3.4 Proxy Details................................................................................................................ 13
3.4.2 Timers ................................................................................................................... 13
3 / 21
[MS-NTHT] — v20090924

3.4.3 Initialization ........................................................................................................... 13
3.4.6 Timer Events.......................................................................................................... 13
4 Protocol Examples ......................................................................................................... 14

4.1 Server Examples .......................................................................................................... 14
4.2 Proxy Examples............................................................................................................ 15
5 Security........................................................................................................................... 17
5.1 Security Considerations for Impleme nters..................................................................... 17
5.2 Index of Security Parameters ....................................................................................... 17
6 Appendix A: Product Behavior ...................................................................................... 18
7 Change Tracking ............................................................................................................ 19
8 Index............................................................................................................................... 20
4 / 21
[MS-NTHT] — v20090924

1 Introduction
Microsoft provides support for NT LAN Manager (NTLM) (as specified in [MS-NLMP]) authentication
in Microsoft Internet Explorer and Microsoft Internet Information Services (IIS) that uses the HTTP
Protocol (for more information, see [RFC2616]) in addition to other standard authentication
mechanisms. This provides the benefits of the NTLM Authentication Protocol for Web applications
when other authentication mechanisms (such as those specified in [RFC4559] and [RFC2617]) are
not available.
Support for NTLM authentication is as specified in [RFC4559], using native NTLM Authentication
Protocol (as specified in [MS-NLMP]) data units instead of encoded tokens (as specified in
[RFC4178]). The tokens are still transmitted using base64 encoding. This document calls out the
differences in the Microsoft implementation from what is specified in [RFC4559], where applicable.
1.1 Glossary
The following terms are specific to this document:
Backus-Naur Form (BNF): Used to describe grammars. Also referred to as "Augmented BNF"
in [RFC2616] section 2.1.
client: Used as described in [RFC2616] section 1.3.
proxy: Used as described in [RFC2616] section 1.3.
server: Used as described in [RFC2616] section 1.3.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as
described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or
SHOULD NOT.
1.2 Refe rences
1.2.1 Normative Re ferences
We conduct frequent surveys of the normative references to assure their continued availability. If
you have any issue with finding a normative reference, please contact [email protected]. We
will assist you in finding the relevant information. Please check the archive site,
http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624, as an
additional source.
[MS-NLMP] Microsoft Corporation, "NT LAN Manager (NTLM) Authentication Protocol Specification",
July 2006.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requireme nt Levels", BCP 14, RFC
2119, March 1997, http://www.ietf.org/rfc/rfc2119.txt
[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC
2616, June 1999, http://www.ietf.org/rfc/rfc2616.txt
[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and
Stewart, L., "HTTP Authentication: Basic and Digest Access Authentication", RFC 2617, June 1999,
http://www.ietf.org/rfc/rfc2617.txt
5 / 21
[MS-NTHT] — v20090924

[RFC4178] Zhu, L., Leach, P., Jaganathan, K., and Ingersoll, W., "The Simple and Protected Generic
Security Service Application Program Interface (GSS-API) Negotiation Mechanism", RFC 4178,
October 2005, http://www.ietf.org/rfc/rfc4178.txt
[RFC4559] Jaganathan, K., Zhu, L., and Brezak, J., "SPNEGO -based Kerberos and NTLM HTTP
Authentication in Microsoft Windows", RFC 4559, June 2006, http://www.ietf.org/rfc/rfc4559.txt
1.2.2 Informative Re fere nces
None.
1.3 Protocol Overvie w (Sy nopsis)
The NTLM over HTTP Protocol authentication variant is similar to the SPNEGO HTTP (as specified in
[RFC4559]) authentication mechanism. Both are used to authenticate a Web client to a Web server.
Although SPNEGO HTTP (as specified in [RFC4559]) works with both Kerberos and NTLM
authentication, the NTLM over HTTP Protocol authentication variant only works with NTLM. The
Kerberos protocol is not supported.
1.4 Relationship to Othe r Protocols
This document is a companion to the SPNEGO HTTP authentication document, as specified in

[RFC4559]. It uses the augmented BNF, as specified in [RFC4559] section 4, and relies on both the
non-terminals defined in that document and other aspects of the specification HTTP/1.1, as specified
in [RFC2617]. For more information, see [RFC2616].
1.5 Prere quisites/Preconditions
NTLM over HTTP Protocol authentication assumes the following in addition to any assumptions
specified in [MS-NLMP].
1. The Web server is operating in an environment with a database of user identities, and the NT
LAN Manager (NTLM) Authentication Protocol, as specified in [MS-NLMP], is available to
authenticate those users.
2. The Web client has implemented the NT LAN Manager (NTLM) Authentication Protocol, as
specified in [MS-NLMP], so that it can participate in user authentication to the Web server.
1.6 Applicability Stateme nt
NTLM HTTP authentication is used in environments where SPNEGO -based Kerberos and NTLM HTTP
authentication, as specified in [RFC4559], are not available, and the Web client and server support
NTLM authentication, as specified in [MS-NLMP].
1.7 Versioning and Capability Negotiation
Versioning and capability negotiation is handled by the HTTP protocols specified in [RFC2617] (for
more information, see [RFC2616]). This protocol has no additional versioning or capability
negotiation.
1.8 Vendor-Extensible Fields
None.
6 / 21
[MS-NTHT] — v20090924

1.9 Standards Assignments
Parameter Value Reference
HTTP auth-scheme NTLM [RFC 2617] section 1.2
7 / 21
[MS-NTHT] — v20090924

2 Messages
2.1 Transport
NTLM over HTTP Protocol messages are carried in the HTTP authentication exchanges as
authentication data (auth-data), as specified in [RFC4559] sections 4.1 and 4.2.
2.2 Message Syntax
The use of NTLM over HTTP Protocol authentication is indicated by an HTTP authentication scheme
(auth-scheme) NTLM. The authentication parameters (auth-params) that are exchanged are
base64-encoded messages. For more details about auth-scheme and auth-params, see [RFC2617]
section 1.2.
2.2.1 WWW-Authenticate Response Header
If the server receives a request for an access -protected object and an acceptable Authorization
Request Header has not been sent, the server MUST respond with a "401 Unauthorized" status code
and a WWW -Authenticate Response Header, per the framework in [RFC2616]. The initial WWW -
Authenticate Response Header MUST NOT carry any auth-data. For more details about the text in
this section, see [RFC2616], and specifically for the 401 status code, see [RFC2616] section 10.4.2.
The NTLM scheme operates as follows.
challenge= "NTLM" auth-data

auth-data = 1#( [ntlm-data] )
The meaning of the value of the directive used above is as follows:
ntlm-data
The ntlm-data directive contains the base64 encoding of a CHALLENGE_MESSAGE, as specified in

[MS-NLMP] section 2.2.1.2.
2.2.2 Authorization Request Heade r
Upon receipt of the response containing a WWW -Authenticate header from the server, the client is
expected to retry the HTTP request with the authorization header, per the framework in [RFC2616]
in the following.
credentials= "NTLM" auth-data2
auth-data2= 1#( [ntlm-data] )
The meaning of the value of the directive used above is as follows:
ntlm-data
8 / 21
[MS-NTHT] — v20090924

The ntlm-data directive contains the base64 encoding of either an AUTHENTICATE_MESSAGE, as
specified in [MS-NLMP] section 2.2.1.3, or a NEGOTIATE_MESSAGE, as specified in [MS-NLMP]
section 2.2.1.1.
Any return code other than a client error HTTP 401 status code (for more information, see
[RFC2616] section 10.4.2), represents successful authentication. If the client is not ab le to access
the requested resource and the response status code is not HTTP 401, the problem is HTTP protocol-
specific (for more information, see [RFC2616] section 10).
2.2.3 Proxy-Authenticate Response Header
If the client must authenticate itself to a proxy and an acceptable proxy-authorization header has
not been sent, the proxy MUST respond with a "407 Proxy Authentication Required" status code (for
more information, see [RFC2616] section 10.4.8) and a "Proxy-Authenticate" header, per the
framework in [RFC2616]. The initial proxy-authenticate header MUST NOT carry any auth-data.
The NTLM scheme operates as follows.
challenge= "NTLM" auth-data3
The meanings of the values of the directives used above are as follows:
ntlm-data
The ntlm-data directive contains the base64 encoding of a CHALLENGE_MESSAGE, as specified in

[MS-NLMP] section 2.2.1.2.
2.2.4 Proxy-Authorization Request Header
Upon receipt of the response containing a proxy-authenticate header from the proxy, the client is
expected to retry the HTTP request with the proxy-authorization header, per the framework in
[RFC2616].
credentials= "NTLM" auth-data4
The meanings of the values of the directives used above are as follows:
ntlm-data
The ntlm_data directive contains the base64 encoding of either an AUTHENTICATE_MESSAGE, as

specified in [MS-NLMP] section 2.2.1.3, or a NEGOTIATE_MESSAGE, as specified in [MS-NLMP]
section 2.2.1.1.
9 / 21
[MS-NTHT] — v20090924

Any return code other than a client error HTTP 407 status code ([RFC2616] section 10.4.2),
represents successful authentication. If the client is not able to access the requested resource an d
the response status code is not HTTP 407, the reason is HTTP protocol-specific. For details, see
[RFC2616] section 10.
10 / 21
[MS-NTHT] — v20090924

3 Protocol Details
3.1 Common Details
3.1.1 Abstract Data Mode l
The abstract data model follows the specifications in [RFC4559].
3.1.2 Timers
None.
3.1.3 Initialization
None.
3.1.4 Highe r-Layer Trigge red Events
None.
3.1.5 Message Processing Events and Sequenc ing Rules
The WWW -Authenticate header is only sent from the server. The Authorization header is only sent
by the client. (For details, see [RFC2617] and also see [RFC2616] sections 14.47 and 14.8.) Clients,
servers, and proxys MUST be compliant with [RFC2617] and [RFC2616].
The Proxy-Authenticate header is only sent from the proxy. The Proxy-Authorization header is only
sent by the client. (For more information, see [RFC2617] and [RFC2616] sections 14.33 and 14.34.)
Clients, servers, and proxys MUST be compliant with [RFC2617] and [RFC2616].
3.1.5.1 Unexpected Messages
Unexpected messages cause the authentication to fail.
If the server receives an unexpected message, it sends an HTTP 401 message to the client.
If the client receives an unexpected message, it does not send a new request to the server.
3.1.6 Timer Events
None.
3.1.7 Other Local Events
There are no local events other than those specified in [RFC4559].
3.2 Serve r Details
11 / 21
[MS-NTHT] — v20090924

3.2.2 Timers
None.
None.
None.
by the client. (For more information, see [RFC2617] and [RFC2616] sections 14.7 and 14.8.)
Servers MUST be compliant with [RFC2617] and [RFC2616].
3.2.6 Timer Events
None.
3.3 C lie nt Details
3.3.2 Timers
None.
None.
None.
12 / 21
[MS-NTHT] — v20090924

3.3.6 Timer Events
None.
3.4 Proxy Details
3.4.2 Timers
None.
None.
None.
3.4.6 Timer Events
None.
13 / 21
[MS-NTHT] — v20090924

4 Protocol Examples
4.1 Serve r Examples
This scenario shows the messages exchanged when a Web client requests an access -protected
document from a Web server using a GET method request at the URL:
http://www.nowhere.org/dir/index.html.
C: GET dir/index.html
The first time the client requests the document, no Authorization header is sent; so the server
responds with the following.
S: HTTP/1.1 401 Unauthorized

S: WWW-Authenticate: NTLM
The client obtains the local user credentials by using the [MS-NLMP] security package and then
generates a new GET request to the server. The request contains an Authorization header with an
NTLM NEGOTIATE_MESSAGE (as specified in [MS-NLMP] section 2.2.1.1) in ntlm-data.
C: Authorization: NTLM tESsBmE/yNY3lb6a0L6vVQEZNqwQn0s8Unew
The server decodes the ntlm-data that is contained in the auth-data2 base64-encoded data and
passes this to its implementation of [MS-NLMP]. If the server accepts this authentication data from
the client, it responds with an HTTP 401 code (for more information, see [RFC2616] section 10.2)
and a WWW -Authenticate header with an NTLM CHALLENGE_MESSAGE (as specified in [MS-NLMP]
section 2.2.1.2) in ntlm-data.
S: HTTP/1.1 401 Unauthorized

S: WWW-Authenticate: NTLM yNY3lb6a0L6vVQEZNqwQn0s8UNew33KdKZvG+Onv
The client decodes the ntlm-data that is contained in the auth-data base64-encoded data and
passes this to its implementation of [MS-NLMP]. If this authentication data is valid, the client
responds by reissuing the GET request with an Authorization header that contains an NTLM
AUTHENTICATE_MESSAGE (as specified in [MS-NLMP] section 2.2.1.3) in ntlm-data.
C: Authorization: NTLM kGaXHz6/owHcWRlvGFk8ReUZKHo=QEZNqwQn0s8U
The server decodes the ntlm-data that is contained in the auth-data2 base64-encoded data and
passes this to its implementation of [MS-NLMP]. If the server accepts this authentication data from
the client, it responds with an HTTP 2xx code (for more information, see [RFC2616] section 10.2)
indicating success. The requested content is also included in the server response.
Note The base64 values used previously are for illustrative purposes only and do not represent
valid base64-encoded NTLM messages.
14 / 21
[MS-NTHT] — v20090924

4.2 Proxy Examples
This scenario shows the messages that are exchanged when a Web client requests an access -
protected document from a proxy using a GET method request at the URL:
http://www.nowhere.org/dir/index.html.
The first time the client requests the document, no Proxy-Authorization header is sent; so the proxy
responds with the following.
S: HTTP/1.1 407 Proxy Authentication Required

S: Proxy-Authenticate: NTLM
The client obtains the local user credentials using the [MS-NLMP] security package and then
generates a new GET request to the proxy. The request contains a Proxy-Authorization header with
an NTLM NEGOTIATE_MESSAGE (as specified in [MS-NLMP] section 2.2.1.1) in ntlm-data.
C: Proxy-Authorization: NTLM tESsBmE/yNY3lb6a0L6vVQEZNqwQn0s8Unew
The proxy decodes the ntlm-data that is contained in the auth-data2 base64-encoded data and
passes this to its implementation of [MS-NLMP]. If the proxy accepts this authentication data from
the client, it responds with an HTTP 407 code (for more information, see [RFC2616] section 10.2)
and a Proxy-Authenticate header with an NTLM CHALLENGE_MESSAGE (as specified in [MS-NLMP]
section 2.2.1.2) in ntlm-data.
S: HTTP/1.1 407 Proxy Authentication Required

S: Proxy-Authenticate: NTLM yNY3lb6a0L6vVQEZNqwQn0s8UNew33KdKZvG+Onv
The client decodes the ntlm-data that is contained in the auth-data base64-encoded data and
passes this to its implementation of [MS-NLMP]. If this authentication data is valid, the client
responds by reissuing the GET request with a Proxy-Authorization header that contains an NTLM
AUTHENTICATE_MESSAGE (as specified in [MS-NLMP] section 2.2.1.3) in ntlm-data.
C: Proxy-Authorization: NTLM kGaXHz6/owHcWRlvGFk8ReUZKHo=QEZNqwQn0s8U
The proxy decodes the ntlm-data that is contained in the auth-data2 base64-encoded data and
passes this to its implementation of [MS-NLMP]. If the proxy accepts this authentication data from
the client, it responds with an HTTP 2xx code (for more information, see [RFC2616] section 10.2)
indicating success. The requested content is also included in the proxy response.
15 / 21
[MS-NTHT] — v20090924

Note The base64 values used previously are for illustrative purposes only and do not represent
valid base64-encoded NTLM messages.
16 / 21
[MS-NTHT] — v20090924

5 Security
5.1 Security Considerations for Impleme nters
The NTLM Authentication Protocol (see [MS-NLMP]) does not provide any facilities for mutual
authentication; therefore, server identities cannot be verified. Other security considerations are as
specified in [RFC4559] section 6.
5.2 Index of Security Parameters
None.
17 / 21
[MS-NTHT] — v20090924

6 Appendix A: Product Behavior
The information in this specification is applicable to the following product versions:
Microsoft Windows NT® operating system
Microsoft Windows® 2000 operating system
Windows® XP operating system
Windows Server® 2003 operating system
Windows Vista® operating system
Windows Server® 2008 operating system
Windows® 7 operating system
Windows Server® 2008 R2 operating system
Exceptions, if any, are noted below. If a service pack number appears with the product version,
behavior changed in that service pack. The new behavior also applies to subsequent service packs of
the product unless otherwise specified.
Unless otherwise specified, any statement of optional behavior in this specification prescribed using
the terms SHOULD or SHOULD NOT implies Windows behavior in accordance with the SHOULD or
SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that Windows does not
follow the prescription.
There are no Windows behavior exceptions in this document.
18 / 21
[MS-NTHT] — v20090924

7 Change Tracking
No table of changes is available. The document is either new or has had no changes since its last
release.
19 / 21
[MS-NTHT] — v20090924

8 Index
A Informative references 6
Initialization
Abstract data model client (section 3.1.3 11, section 3.3.3 12)
client (section 3.1.1 11, section 3.3.1 12) proxy (section 3.1.3 11, section 3.4.3 13)
proxy (section 3.1.1 11, section 3.4.1 13) server (section 3.1.3 11, section 3.2.3 12)
server (section 3.1.1 11, section 3.2.1 11) Introduction 5
Applicability 6
Authorization request header 8 L
C Local events
client (section 3.1.7 11, section 3.3.7 13)
Capability negotiation 6 proxy (section 3.1.7 11, section 3.4.7 13)
Change tracking 19 server (section 3.1.7 11, section 3.2.7 12)
Client
abstract data model (section 3.1.1 11, section M
3.3.1 12)
higher-layer triggered events (section 3.1.4 11, Message processing
section 3.3.4 12) client (section 3.1.5 11, section 3.3.5 12)
initialization (section 3.1.3 11, section 3.3.3 12) proxy (section 3.1.5 11, section 3.4.5 13)
local events (section 3.1.7 11, section 3.3.7 13) server (section 3.1.5 11, section 3.2.5 12)
message processing (section 3.1.5 11, section Messages
3.3.5 12) syntax 8
sequencing rules (section 3.1.5 11, section 3.3.5 transport 8
12)
timer events (section 3.1.6 11, section 3.3.6 13) N
timers (section 3.1.2 11, section 3.3.2 12)
Normative references 5
D
O
Data model - abstract
client (section 3.1.1 11, section 3.3.1 12) Overview 6
proxy (section 3.1.1 11, section 3.4.1 13)
server (section 3.1.1 11, section 3.2.1 11) P
E Parameters - security index 17

Preconditions 6
Examples Prerequisites 6
proxy 15 Product behavior 18
server 14 Proxy
abstract data model (section 3.1.1 11, section
F 3.4.1 13)
examples 15
Fields - vendor-extensible 6 higher-layer triggered events (section 3.1.4 11,
section 3.4.4 13)
G initialization (section 3.1.3 11, section 3.4.3 13)
local events (section 3.1.7 11, section 3.4.7 13)
Glossary 5 message processing (section 3.1.5 11, section
3.4.5 13)
H sequencing rules (section 3.1.5 11, section 3.4.5
13)
Higher-layer triggered events timer events (section 3.1.6 11, section 3.4.6 13)
client (section 3.1.4 11, section 3.3.4 12) timers (section 3.1.2 11, section 3.4.2 13)
proxy (section 3.1.4 11, section 3.4.4 13) Proxy-Authenticate response header 9
server (section 3.1.4 11, section 3.2.4 12) Proxy-authorization request header 9
I R
Implementer - security considerations 17 References

Index of security parameters 17 informative 6
20 / 21
[MS-NTHT] — v20090924

normative 5
Relationship to other protocols 6
Security
implementer considerations 17
parameter index 17
Sequencing rules
server (section 3.1.5 11, section 3.2.5 12)
Server
abstract data model (section 3.1.1 11, section
3.2.1 11)
examples 14
higher-layer triggered events (section 3.1.4 11,
section 3.2.4 12)
initialization (section 3.1.3 11, section 3.2.3 12)
local events (section 3.1.7 11, section 3.2.7 12)
message processing (section 3.1.5 11, section
3.2.5 12)
sequencing rules (section 3.1.5 11, section 3.2.5
12)
timer events (section 3.1.6 11, section 3.2.6 12)
timers (section 3.1.2 11, section 3.2.2 12)
Standards assignments 7
Syntax 8
Timer events
Timers
Tracking changes 19
Transport 8
Triggered events - higher-layer
Vendor-extensible fields 6
Versioning 6
WWW-Authenticate response header 8
21 / 21
[MS-NTHT] — v20090924

NTLM Over HTTP Protocol Specification

Uploaded by

Copyright:

Available Formats

NTLM Over HTTP Protocol Specification

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NTLM Over HTTP Protocol Specification

Uploaded by

Copyright:

Available Formats

[MS-NTHT]:

NTLM Over HTTP Protocol Specification

Intellectual Property Rights Notice for Open Specifications Documentation

 Technical Documentation. Microsoft publishes Open Specifications documentation for

 Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

03/14/2007 1.0 Version 1.0 release

04/10/2007 1.1 Version 1.1 release

05/18/2007 1.2 Version 1.2 release

06/08/2007 1.2.1 Editorial Revised and edited the technical content.

07/10/2007 1.2.2 Editorial Revised and edited the technical content.

08/17/2007 1.2.3 Editorial Revised and edited the technical content.

09/21/2007 1.2.4 Editorial Revised and edited the technical content.

01/25/2008 2.0.1 Editorial Revised and edited the technical content.

03/14/2008 2.0.2 Editorial Revised and edited the technical content.

06/20/2008 3.0 Major Updated and revised the technical content.

07/25/2008 3.1 Minor Updated the technical content.

08/29/2008 3.1.1 Editorial Revised and edited the technical content.

10/24/2008 3.1.2 Editorial Revised and edited the technical content.

12/05/2008 4.0 Major Updated and revised the technical content.

01/16/2009 4.0.1 Editorial Revised and edited the technical content.

02/27/2009 4.0.2 Editorial Revised and edited the technical content.

04/10/2009 4.0.3 Editorial Revised and edited the technical content.

05/22/2009 4.0.4 Editorial Revised and edited the technical content.

07/02/2009 4.1 Minor Updated the technical content.

08/14/2009 4.2 Minor Updated the technical content.

09/25/2009 4.2.1 Editorial Revised and edited the technical content.

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

4 Protocol Examples ......................................................................................................... 14

6 Appendix A: Product Behavior ...................................................................................... 18

7 Change Tracking ............................................................................................................ 19

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

The following terms are specific to this document:

client: Used as described in [RFC2616] section 1.3.

proxy: Used as described in [RFC2616] section 1.3.

server: Used as described in [RFC2616] section 1.3.

1.2 Refe rences

1.2.1 Normative Re ferences

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

1.2.2 Informative Re fere nces

1.3 Protocol Overvie w (Sy nopsis)

1.4 Relationship to Othe r Protocols

This document is a companion to the SPNEGO HTTP authentication document, as specified in

1.5 Prere quisites/Preconditions

1.6 Applicability Stateme nt

1.7 Versioning and Capability Negotiation

1.8 Vendor-Extensible Fields

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

Parameter Value Reference

HTTP auth-scheme NTLM [RFC 2617] section 1.2

Copyright © 2009 Microsoft Corporation.

Release: Thursday, September 24, 2009

2.2 Message Syntax