Setting Security Overview

When building Web Service applications, there is a challenge in building scalable applications that are secure. You can secure Web Services by having the message sent over a secure transport, such as Secure Sockets Layer (SSL), but this is limited to point-to-point communication.

To allow you to send your messages securely, VuGen supports several security mechanisms, Security Tokens (WS-Security), and SAML.

The following table lists the considerations for using each of the models.

Legacy Model
Scenario Based Model
You are working with a script that already uses the legacy model
You are testing a WCF Service.
You are testing a service written in frameworks such as .NET 2.0, Axis, or other older toolkits
You are testing a service written in a new framework, such as Axis2 or Metro (WSIT).
You require a low-level control over WS-Security tokens
Your service uses advanced specifications such as WS-SecureConversation or WS-Trust.
You are having trouble using the new model or find the capabilities of the legacy more adequate for your needs
You are having trouble using the legacy model or you find the capabilities of the new model more adequate.

Note: If your WSDL is located in a secure location, you must provide the security information through the Manage Services dialog box. For more information, see the Connection Settings Dialog Box.

See also:

Back to top