No Security Token Service is contacted.
未联系到任何安全令牌服务。
Secure communication with the security token service using SSL
使用SSL保护与安全令牌服务之间的通信
Security token Service: Package and transit output claims using REST tokens.
安全令牌服务：使用REST令牌把声明打包和转换。
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)。
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.
用户端验证系以安全性权杖服务对用户端发行的权杖为基础。
The sample configuration includes a client, provider, and security token service (STS) configured, as shown in Figure 1.
样例配置中包含一个客户端、提供者和已配置的安全令牌服务 (Security Token Service，STS)，如图 1 所示。
Use this property to specify the endpoint address and binding to use when contacting your local Security Token Service.
使用这个属性，即可指定要在连络本机安全性权杖服务时使用的端点位址和系结。
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服务进行交换。
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消息安全方式提供，并根据由安全令牌服务颁发给客户端的令牌进行。
When obtaining an issued token from a Security token Service, the client application must be configured with the address of the Security token Service.
从安全性权杖服务取得核发的权杖时，用户端应用程序必须以安全性权杖服务的位址加以设定。
Securing the communication with the Tivoli Federated Identity Manager security token service is recommended to protect the integrity and confidentiality of the message.
建议保护与TivoliFederatedIdentityManager安全令牌服务之间的通信，以保护消息的完整性和私密性。
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.
当从安全令牌服务获取已颁发的令牌时，必须使用该绑定配置客户端应用程序，以用于与安全令牌服务进行通信。
Although WebSphere Application Server could directly contact an Security Token Service, the Figure 6 shows how the sample scenario evolves after the STS component introduction.
虽然WebSphereApplicationServer可直接联系安全令牌服务，但是图6显示了样例场景如何在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)的引导程序消息交换和与服务的实际会话，策略使用不同的算法套件。
The client's secured initial request containing the SAML security token is sent to the service.
客户端包含SAML安全令牌的受保护初始请求被发送给服务。
This is used by a Web service for additional challenges to a requester to ensure message freshness and verification that the use of a security token is authorized.
这种机制由Web服务用来对请求者进行更多质询，以确保消息不过时，以及验证安全令牌的使用是否已经授权。
The only difference is that, after you perform the standard security configuration, you need to secure the Web service by specifying the use of the LTPA token.
唯一的区别在于，在进行了标准的安全配置之后，您需要通过指定 LTPA 令牌的使用来确保Web服务的安全。
This means that all requests against the Web service interface must contain a security token, which represents a valid user authentication.
这意味着对Web服务接口的所有请求必须包含一个安全令牌，安全令牌代表有效的用户凭证。
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服务提供者。
You now have specified that the UsernameToken to be passed in the SOAP header according to the WS-Security specification is to be used as the authentication token by the service provider.
根据WS - Security规范，您现在已经将在SOAP头部传递的UsernameToken指定为供服务提供者使用的身份验证令牌。
The sample Web service provider application is configured to use WS-Security with a lightweight Third Party Authentication (LTPA) token.
实例Web服务提供者应用程序配置为通过轻量级第三方认证（Lightweight Third Party Authentication，LTPA）令牌使用WS-Security。
In the detail implementation, several techniques are adopted to insure the system security, including TLS protocol and a Local Application Service Token creation method.
在具体实现上，采用多种技术保证系统的安全性，包括TLS协议，本地应用服务令牌生成方法等。
In the detail implementation, several techniques are adopted to insure the system security, including TLS protocol and a Local Application Service Token creation method.
在具体实现上，采用多种技术保证系统的安全性，包括TLS协议，本地应用服务令牌生成方法等。
应用推荐