Figure 6 shows a WS-security architecture.
图6显示了WS - security体系结构。
Secure internal communication using SOAP with WS-security
安全的内部通信，使用SOAP和WS-Security
Username: WS-Security plain-text UsernameToken on requests.
username：请求中使用WS - Security纯文本usernametoken。
Username - WS-Security plain-text UsernameToken on requests.
username—在请求上的WS - Security纯文本usernametoken。
The example above is an entry-level WS-Security architecture.
上面例子是入门级的WS-Security体系结构。
Understanding web Services specifications, Part 4: ws-security.
了解Web服务规范：第4部分：WS - security。
For WS-Security authentication, encryption and signing are supported.
对于WS - Security身份验证，支持加密和签名。
Select WS-Security => Authentication and protection => gen_saml20token.
选择WS-Security =>Authenticationandprotection => gen_saml20token。
Using WS-Security, on the other hand, causes some huge drops in performance.
另一方面，使用WS-Security会造成性能显著降低。
A WS-Security policy needs to be created and applied to the Gateway service.
需要创建一个WS - Security策略并把它应用于Gateway服务。
The WS-Security configuration error will no longer occur in the console logs.
WS - Security配置错误不会再出现在控制台日志中。
After the wizard completes, you can configure the WS-Security client bindings.
向导完成后，可以配置WS - Security客户机绑定。
Another way of using message integrity is using WS-Security for the Web services.
实现消息完整性的另一种方法是对Web服务使用WS - Security。
Using the WAS Console, we will ensure that the WS-Security is no longer configured.
通过使用WAS控制台，我们将确保不再配置WS - Security。
In this article, you'll see two examples of configuring WS-Security handling in CXF.
在本文中，您会看到在CXF中配置WS - Security处理的两个示例。
A Policy Set editor is provided which enables declaration of WS-Security capabilities.
提供的策略集编辑器可以声明WS - Security功能。
This is configured in the client policy set binding for WS-Security in Process Server.
这在Process Server中的WS - Security的客户端策略集绑定中配置。
They are compatible with other runtimes that support the WS-Security proposed standard.
它们与支持WS - Security提议标准的其他运行时兼容。
signencr: WS-Security signing of body and headers, with timestamp, and encryption of body
signencr：主体和头部的WS-Security签名，使用时间戳和主体加密
The WCF Client will be configured to use WS-Security when invoking the (gateway) service.
要配置WCF客户机，让它在调用(网关)服务时使用WS - Security。
Signencr: WS-Security signing of body and headers, with timestamp and encryption of body.
signencr：WS - Security主体和报头签名，使用时间戳和主体加密。
Is compliance to a security standard security, such as Kerberos or WS-Security, required?
是否需要遵守行业安全标准，例如Kerberos或WS - Security ？
This implementation of WS-Security was based on the OASIS working draft 13 specification.
WS - Security的这个实现基于OASIS工作草案13规范。
Proxy mode deployments may not specify a WS-Security configuration for the target service.
而代理模式部署不能为目标服务指定WS-Security配置。
Signencr - WS-Security signing of body and headers, with timestamp, and encryption of body.
signencr—有时间戳和主体加密的WS - Security主体和头部签名。
This article explained some of the concepts of WS-Security with regard to signing a message.
本文阐述了一些有关对消息进行签名的WS - Security概念。
Enter % install % \ etc \ ws-security \ samples \ enc-sender.jceks in the Key Store Path field.
在KeyStorePath字段中输入%install % \etc \ws - security \samples \enc - sender . jceks。
As mentioned, tokens are placed in a WS-Security header inside the SOAP: envelope header element.
正如前面提到的，令牌被放在WS - Security标头的SOAP：envelope标头元素中。
A major part of the WS-Security performance cost comes from the wide use of asymmetric encryption.
WS - Security之所以常常伴随性能损失主要是因为大量使用了非对称加密。
WS-Security is a standard for adding security to SOAP Web service message exchanges (see Resources).
WS - Security是向SOAPWeb服务消息交换添加安全性的一种标准(见参考资料)。
应用推荐