大网数据广告活动
账户与安全

Maintaining the Security Context Between Connections

· 52CE 我爱测

To reduce domain controller traffic and improve performance, the client-side of Microsoft Digest caches information received after successful authentication with a server.

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.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 09/14/2022
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。