Microsoft Digest performs an initial authentication when the server receives the first challenge response from a client. The server verifies that the client has not been authenticated and then performs the initial authentication by accessing the services of a domain controller. For a detailed description of this procedure, see Initial Authentication using Microsoft Digest.

When the initial authentication is successful the server receives a Digest session key. The server caches this key and uses it to authenticate subsequent requests for resources from the client. This authentication is local, that is, it does not require access to a domain controller. For a detailed description of this procedure see Authenticating Subsequent Requests using Microsoft Digest.

When using HTTP, there is no connection maintained between client and server. To reduce domain controller traffic and improve performance, Microsoft Digest caches information received after successful authentication. For information about this process, see Maintaining the Security Context Between Connections.

Send comments about this topic to Microsoft

Build date: 6/26/2009