Web Service Attributes Editor: Secure Token Service

See Also 

In the WSIT tab's Secure Token Service section, on the client side, you can define a service that implements the protocol defined in the WS-Trust specification. This protocol defines message formats and message exchange patterns, and contains a set of interfaces to be used for the issuance, exchange, and validation of security tokens. STS enables the use of multiple security token formats to accommodate a variety of authentication and authorization mechanisms. An issuing STS takes an input request (including proof of identity) and responds with a token that the named identity has requested.

You can set the following options:

• Endpoint. The endpoint of the STS.
• WSDL Location. The location of the WSDL for the STS.
• Metadata. The metadata address for the STS.
• Service Name. The service name of the STS.
• Port Name. The port name of the STS.
• Namespace. The namespace for the service in the WSDL.

Note: Endpoint is a mandatory field. For the others, you can provide either Metadata information or information regarding the WSDL Location, Service Name, Port Name and Namespace.

The following is an example STS configuration:

• Endpoint:
  http://131.107.72.15//Security_Federation_SecurityTokenService_Indigo/Symmetric.svc/Scenario_2_IssuedToken_MutualCertificate10
• WSDL Location:
  http://131.107.72.15//Security_Federation_SecurityTokenService_Indigo/Symmetric.svc?wsdl
• Service Name:
  SecurityTokenService
• Port Name:
  CustomBinding_ISecurityTokenService
• Namespace:
  http://tempuri.org/