大网数据广告活动
网络与域名解析

MSMQ Security Services

· 52CE 我爱测

Synchronous RPC messages can use any of the security features available from the RPC run time. See Security for more details.

Synchronous RPC messages can use any of the security features available from the RPC run time. See Security for more details.

Asynchronous [ message] calls cannot use RPC security because there is no handshake between client and server. In fact, the server may not even be running at the time of the call. To access the security services provided by Message Queuing Services (MSMQ), the client application should call RpcBindingSetAuthInfo to control the level of authentication and privacy for its calls to the server.

The server application can call RpcBindingInqAuthClient from within a remote procedure call to determine the security level for that call. The mapping between RPC security constants and MSMQ security is shown in the following table.

RPC security level Description
RPC_AUTHN_LEVEL_NONE The call is not authenticated or encrypted.
RPC_AUTHN_LEVEL_PKT_INTEGRITY The call is authenticated using MSMQ security.
RPC_AUTHN_LEVEL_PKT_PRIVACY The call is authenticated and encrypted as it travels between the client and server queue.

The server can also force call authentication and encryption by calling RpcServerUseProtseqEpEx and setting the RPC_C_MQ_AUTHN_LEVEL_NONE, RPC_C_MQ_AUTHN_LEVEL_PKT_INTEGRITY and RPC_C_MQ_AUTHN_LEVEL_PKT_PRIVACY flags in the RPC_POLICY structure.

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 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

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

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