Secure communication with the security token service using SSL
使用SSL保护与安全令牌服务之间的通信
For security token service modules: com.tivoli.am.fim.trustserver.sts.modules.*=all
对于安全令牌服务模块：com.tivoli.am.fim.trustserver.sts.modules.*=all
This is a security token service (STS), as defined in the OASIS WS-Trust specification.
这是一个OASISWS - Trust规范中定义的安全令牌服务(STS)。
The sample configuration includes a client, provider, and security token service (STS) configured, as shown in Figure 1.
样例配置中包含一个客户端、提供者和已配置的安全令牌服务 (Security Token Service，STS)，如图 1 所示。
Securing the communication with the Tivoli Federated Identity Manager security token service is recommended to protect the integrity and confidentiality of the message.
建议保护与TivoliFederatedIdentityManager安全令牌服务之间的通信，以保护消息的完整性和私密性。
Represents information used to obtain an issued token from a security token service.
表示用于从安全令牌服务获取已颁发令牌的信息。
Client authentication is based on the token issued to the client by a security token service.
用户端验证系以安全性权杖服务对用户端发行的权杖为基础。
Client authentication is provided by means of SOAP message security and is based on the token issued to the client by a security token service.
客户端身份验证采用SOAP消息安全方式提供，并根据由安全令牌服务颁发给客户端的令牌进行。
No Security Token Service is contacted.
未联系到任何安全令牌服务。
Security token Service: Package and transit output claims using REST tokens.
安全令牌服务：使用REST令牌把声明打包和转换。
These messages can be exchanged by clients calling a particular type of SOAP web service called a Security Token service (STS).
这些消息可以由客户机通过调用一种称为Security Token Service (STS)的特定类型的SOAPWeb服务进行交换。
When obtaining an issued token from a Security token Service, the client application must be configured with the binding to use to communicate with the Security token Service.
当从安全令牌服务获取已颁发的令牌时，必须使用该绑定配置客户端应用程序，以用于与安全令牌服务进行通信。
The problem in this case was that the policy used different algorithm suites for the bootstrap message exchange with the Security Token service (STS) and the actual conversation with the service.
在这种情况下问题是，对于与Security Token Service (STS)的引导程序消息交换和与服务的实际会话，策略使用不同的算法套件。
The problem in this case was that the policy used different algorithm suites for the bootstrap message exchange with the Security Token service (STS) and the actual conversation with the service.
在这种情况下问题是，对于与Security Token Service (STS)的引导程序消息交换和与服务的实际会话，策略使用不同的算法套件。
应用推荐