Maintaining the Security Context Between Connections
Note
Starting in Windows 11 22H2, Microsoft is deprecating Microsoft Digest, also known as wDigest. We will continue to support Microsoft Digest on supported versions of Windows. Future versions of Windows will include limited capabilities for Microsoft Digest, and eventually Microsoft Digest will no longer be supported on Windows.
To reduce domain controller traffic and improve performance, the client-side of Microsoft Digest caches information received after successful authentication with a server. Client applications need only cache the handle to the security context that has been established. The following table describes information cached by the security package.
| Information | Description |
|---|---|
| Server name | The server that has successfully created a security context for the user. |
| Realm/Domain | The domain name used in the successful authentication. |
| Nonce | A server nonce that is associated with the successful authentication. |
| Nonce count | The number of times the client has included the nonce in requests to the server. This is used for replay-detection. |
| Opaque value | The value returned for the opaque directive after a successful authentication. This value contains a reference to the security context of the user. |
When a client sends a message to a server, the server must determine whether the client has an existing security context. To do this, the server passes each client request to the AcceptSecurityContext (General) function. This function extracts the value of the opaque directive from the request, if present, and uses it to look up the client's security context. If the security context is found, the handle of the context is returned to the server. For related information, see Authenticating Subsequent Requests.
As a means of detecting spoofing and replay attacks, the client calls the MakeSignature function which uses a security context to sign a message. When messages are protected using the MakeSignature function, the server uses the VerifySignature function with the cached context to verify the message's origin and integrity. For more information, see Protecting Messages.