WCF Service scenarios

In addition to the default Web service scenario, you can select from one of the following WCF-type service scenarios.

WCF Service (CustomBinding) Scenario

The WCF Service (CustomBinding) scenario enables the highest degree of customization. Because it is based on the WCF CustomBinding standard, it enables you to test most WCF services, along with services on other platforms such as Java-based services that use the WS - <spec_name> specifications.

Use the WCF Service (CustomBinding) scenario to configure a scenario that does not comply with any of the predefined security scenarios. You can customize the transport and encoding settings:

  • Transport.HTTP, HTTPS, TCP, or NamedPipe

  • Encoding.Text, MTOM, or WCF Binary

You can also provide additional security information:

Authentication mode

The type of authentication, such as None, AnonymousForCertificate.

The options are available from the drop down list.
Bootstrap policy For the SecureConversation authentication mode, you can specify a bootstrap policy.
Net Security

The network security for TCP and NamedPipe type transports.

Typical values are None, Windows stream security, or SSL stream security available from the field's drop down list.

For services with HTTP transport, you should set the value to None. To enable SSL for HTTP, select HTTPS transport.

Note: For WSE3 security configurations, use the WCF Service(CustomBinding) Scenario.

For details, see Customize security for WCF-type Web services.

Back to top

WCF Service (Federation) Scenario

In the WCF Service (Federation) scenario, the client authenticates against the STS (Security Token Service) to obtain a token. The client uses the token to authenticate against the application server.

Therefore, two bindings are needed, one against the STS and another against the application server.

You define the bindings in two stages:

  • Provide security details for the application server's security scenario in the following areas:

    Server The transport and encoding methods.
    Security The authentication mode, such as IssuedToken, SecureConversation.
    Identity Information about the server certificate and expected DNS.
    STS Settings related to the STS, such as the endpoint address and binding.

  • Define an STS binding in the Referenced binding field.

For task details, see Customize security for WCF-type Web services.

Back to top

WCF Services (WSHttpBinding) Scenario

In the WCFService (WSHttpBinding) scenario, you can select from several types of authentication: None, Windows, Certificate, or Username (message protection).

No Authentication (Anonymous)

In this scenario, the client uses the server's certificate to encrypt a message; there is no client authentication. Use this scenario to test Web Services where the:

  • Client uses the server's X.509 certificate for encryption.

  • Client is not authenticated.

  • Communication may utilize advanced standards such as secure conversation or MTOM.

Windows Authentication

This scenario uses Windows Authentication. If you are testing a WCF service that has not been customized and uses the default configuration, use this type of scenario.

Use this scenario to test Web Services where the:

  • Client and server use Windows authentication.

  • Security is based on Kerberos or SPNEGO negotiations.

  • Communication may utilize advanced standards such as secure conversation or MTOM.

Certificate Authentication

In this WCF WSHttpBinding scenario, the client uses the server's X.509 certificate to encrypt the message and its own certificate for a signature.

Use this scenario to test Web Services where the:

  • Client uses the server's X.509 certificate for encryption.

  • Client uses its own X.509 certificate for signatures.

  • Communication may utilize advanced standards such as secure conversation or MTOM.

Username Authentication (Message Protection)

In the WCF WSHttpBinding scenario, the client uses the server's X.509 certificate to encrypt the message, and sends a user name and password to authenticate itself.

Use this scenario to test Web Services where the:

  • Client uses the server's X.509 certificate for encryption.

  • Client is authenticated with a username and password.

  • Communication may utilize advanced standards such as secure conversation or MTOM.

Back to top