Scenario categories

The scenario describes the configuration of your Web Service. It contains information such as security, encoding, and proxy. VuGen provides a Security Scenario editor that allows you to configure the settings for each scenario.

To determine the scenario that best fits your service, refer to the sections below. If you are unsure which scenario to choose, we recommend to use the Custom Binding scenario. For more information, see Custom Binding scenario.

Use the default <no scenario> for:

  • simple Web Services where no advanced standards are required.

  • scripts that use the legacy security model

  • Web Services that require a specific security setting, not available in any of the existing scenarios.

If you select a built-in scenario and experience problems in replay, it is possible that no scenario was required and the problem is elsewhere. Reset the value to <no scenario>.

The built-in security scenarios are divided into the following categories:

Core scenarios

The following table describes the built-in Core scenario.

Scenario Name
When to use
Plain SOAP

  • Web Services which do not require advanced standards

  • Web Services which may require you to specify the WS-Addressing version

For this type of scenario, if your service uses WS-Addressing, specify the version.

Security scenarios

The following table describes the built-in Security scenario.

Scenario Name
When to use
Username Authentication

  • Client is authenticated with a username and password on the message level

For this type of scenario, specify the username/password, and if your service uses WS-Addressing, specify the version.

WCF scenarios

The following table shows the scenarios for Web Services that utilize WCF. The WSHttpBinding-based scenarios are divided according to the way the client authenticates itself to the server. For example, if your client presents a user name and a password to the server, choose the Username (message protection) scenario. The user interface lets you provide the identity information in the form of a user name or a certificate as required.

WCF Scenario Name
When to use
WSHttpBinding - No Authentication

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

  • Client is not authenticated

  • Communication may utilize advanced standards such as secure conversation and MTOM
WSHttpBinding - Windows authentication

  • Client and server use Windows authentication

  • Security is based on Kerberos or SPNEGO negotiations

  • Communication may utilize advanced standards such as secure conversation and MTOM
wsHttpBInding - Certificate authentication

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

  • Client uses its own X.509 certificate for signature

  • Communication may utilize advanced standards such as secure conversation and MTOM
WSHttpBinding - username (message protection) authentication

  • 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 and MTOM
WSHttpBinding - username (transport protection) authentication

  • SSL is enabled

  • Client is authenticated with a username and password

  • Communication may utilize advanced standards such as secure conversation and MTOM
WSFederationHttpBinding

  • Client authenticates against the STS using a predefined scenario

  • Client uses the token given from the STS to authenticate against the server
Custom Binding

  • Web Service that uses WS-* standards

  • WCF services of any configuration

Optimization Scenarios

The following table describes the built-in Optimization scenario.

Scenario Name
When to use
MTOM

  • MTOM-enabled Web Services

  • Web Services which may require you to specify the WS-Addressing version

For MTOM type scenarios, if your service uses WS-Addressing, specify the version.

Back to top