Ensure Include timestamp in security header is checked.
确认选中Includetimestamp insecurity header。
DWS allows the passing of security header tokens in the SOAP message headers.
DWS允许在SOAP消息报头中传递安全报头标志。
Adds a SAML Authentication Assertion (encapsulated into a WS-Security header) containing.
添加SAML验证断言(封装成的WS - Security标头)，其中包括。
The third item in the security header is a <ds:Signature> block, with three child elements.
安全头部中的第三个项是一个 <ds:Signature>块，其中包含三个子元素。
The first difference is the presence of a <xenc:EncryptedKey> element in the security header.
第一个不同是在安全头部中出现了 <xenc:EncryptedKey>元素。
As mentioned, tokens are placed in a WS-Security header inside the SOAP: envelope header element.
正如前面提到的，令牌被放在WS - Security标头的SOAP：envelope标头元素中。
The original SOAP body element is moved to a newly added bogus wrapper element in the SOAP security header.
原始soap消息体元素会被转移到SOAP安全消息头的一个新添加的伪造包装器元素中。
Figure 7 shows an architecture in which a gateway on the server side ACTS in a role assigned to the WS-Security header.
图7显示了服务器端网关具有指定给WS - Security Header的角色的体系结构。
The provider gateway will take this DN and propagate it to the Web service provider in an LTPA token inside a WS-Security header.
提供者网关将采用此DN，并将其传播给WS安全标头中ltpa令牌中的Web服务提供者。
Figure 8 shows an architecture in which a gateway on the server side is not acting in role assigned to the WS-Security header.
图8显示了服务器端网关不具有指定给WS - Security Header的角色的体系结构。
Protocol channels handle support for specific QoS characteristics, for example, security channel encrypts message and adds security header.
协议信道(Protocol channels)用于支持特定的QoS特性，如安全信道加密消息和增加安全头。
If you want to propagate your security information only as far as a particular intermediary, you can address a particular WS-Security header to that actor.
如果您只是想把安全性信息传播到一个特定的中介体，您可以为该操作者指定一个特定的WS - security头。
This encrypted data element references the <xenc:EncryptedKey> value from the security header as the key for the symmetric encryption used on the Body content.
这个已加密的数据从安全头部引用 <xenc:EncryptedKey>值作为在Body内容中用于对称加密的密匙。
To allow your Web service to work over various underlying protocols, make use of the WS-Security header for authentication, as it is passed with all protocols.
要使您的Web服务能够在各种底层协议上工作，请使用WS - Security头进行认证，因为这个头可以用所有的协议发送。
Security header tokens and trusted context are important features to consider when choosing and implementing the security model for your Web services environment.
当为Web服务环境选择和实现安全模型时，安全报头标记和受信任上下文都是要重点考虑的特性。
Remove Security Header [request] This removes WS-Security Header, wsse: Security, from request message before the device sends the message to back-end server.
RemoveSecurity Header [request]设备将消息发送到后端服务器之前，此参数将从请求消息中删除ws - Security Header的wsse： Security。
By default, Message Broker will extract identity from the appropriate location for a particular transport such as MQ user identity or Web services security header.
缺省情况下，MessageBroker将从特定传输的适当位置提取标识，例如MQ用户标识或Web服务安全标头。
This is the same as the gateway on server side acting in role assigned to the WS-Security header architecture but with the XS40 substituted for the Web Services Gateway.
这与服务器端网关具有指定给WS-Security Header 的角色体系结构相同，但其中使用XS40代替Web服务网关。
The last step implements the message transformation, here we remove the WS-Security header and generate an LTPA token (at the transport level) built on the mapped identity (the role "Guest").
最后一步实现了消息转换，在这里，我们删除了WS - Security头并生成一个建立在映射身份(角色“Guest”)上的ltpa令牌(在传输级别)。
For instance, a policy that receives a SOAP request validates security information in the SOAP header to validate that a user may receive previously cached response data.
例如，收到一个SOAP请求时的策略，这个策略会在SOAP消息头里验证安全信息来确认用户也许可以接受先前缓存的响应数据。
You are going to test two scenarios: one for testing message flow security functions using the identity extracted from the HTTP header.
您将测试两个场景：一个使用从HTTP报头中提取的身份测试消息流安全性功能。
In tunnel mode, the inner IP header carries the intended source and original destination addresses, while an outer IP header contains IP addresses for hop points such as security gateways.
在隧道模式，内部的ip报头承载预设的源和最初的目的地址，外部ip报头包含用于跳点的IP地址，比如安全网关。
Once the message has been signed, the X.509 certificate itself is included in the SOAP header as a binary security token.
一旦消息被签名，X . 509证书本身就作为二进制安全性令牌包含进soap头了。
Include the security plug-in header files in your plug-in.
将安全性插件的头文件包括到插件中。
For identification, you can use WS-Security Username token embedded into the header of the SOAP message sent by the client application.
对于身份验证，您可以使用嵌入到SOAP消息的头部并由客户端应用程序发送的WS - SecurityUsername令牌。
Figure 5 shows the location of the two required header files for implementing security plug-ins on a Windows system.
图5展示了在Windows系统上实现安全性插件所需的这两个头文件的位置。
Step 1: Include the security plug-in header files in your plug-in.
步骤1：将安全性插件头文件包括到插件中。
Examine security functions for identity extracted from the HTTP header.
检查从HTTP报头中提取的身份的安全性功能。
The <wsse:Security> header within the SOAP message holds all the run-time security configuration information and signature data.
SOAP消息中的 <wsse:Security>头部保存有所有运行时安全配置信息和签名数据。
WS-Security has standardized header blocks, known as tokens, that can be used to store this information.
WS-Security已经标准化了可用于存储此信息的标头块（也称为令牌）。
应用推荐