Microsoft . Web Services Enhancements 3.0 for .NET (WSE) enables developers to create interoperable web services with advanced web service capabilities. With WSE 3.0, you can secure messages with digital signatures and encryption, efficiently send large amounts of binary data using MTOM, route messages through intermediaries, host web services outside of IIS, use TCP/IP protocols, and more. WSE 3.0 comes with examples and product documentation. For more information, visit the WSE home page on MSDN.
Key features of version 3.0
• By providing a "turnkey security scenario", you can provide a higher level of security building blocks that make security at the message level, allowing you to secure the messaging pattern without having to think about how to secure requests and respond to messages independently. These "turnkey security solutions," also known as security assertions, are industry best practices when securing end-to-end messages.
Interoperability with Windows Communication Foundation (WCF). WSE3.0 aligns with WCF on the same set of Web service specifications (see product documentation for a complete list), enabling line-level interoperability of messages. In addition, security has been simplified and relevant API names have been adjusted so that conceptually WSE 3.0 provides many of the security features available in WCF. WSE 3.0 policies are similar to WCF bindings. WCF clients can communicate with WSE 3.0 web services, while WSE 3.0 clients can communicate with WCF services.
• Comprehensive policy framework
The Policy policy file format has been simplified to reflect the TurnkeySecurity scenario. Policies still allow configuration-based claims for security requirements for incoming and outgoing SOAP messages, but policies now focus on where to get security tokens based on the security claims you choose.
◾ Programming based on CLR properties. You can now associate a policy file with a client agent or service by applying a policy attribute, i.e. [Policy("ServerPolicy")]
Policy has adapted the imperative and declarative programming model of policy to provide a unified programming abstraction. In WSE 2.0, there is no association between the code written to ensure message exchange and the declarative policy file. In WSE 3.0, policy files can be used in code to secure clients or services by using the CLRPolicy property and the SetPolicy method in the WSE-generated client agent (via Visual Studio's Add Web Reference or using wsewsdl3.exe command-line tools).
OLIC policies also provide an important extension mechanism for user-defined or custom policies in your code. Custom transformations of SOAP envelopes can be performed at any stage of the pipeline by extending the Microsoft.Web.Services3.Design.PolicyAssertion class to create your own policy statements. For example, this allows you to define a logging assertion or have a policy assertion that can enforce a specified XML schema for message validation. The same assertions can then be used in the declarative policy file. You can also extend the built-in policy security statements to tailor your turnkey security approach to your needs. For example, add additional support tokens to the message. An example of a custom policy is provided in the quickstart example.
The updated Security Setup Wizard helps protect applications with a series of simple steps to generate policiesThe Security Setup Wizard asks questions to select the most appropriate turnkey security scenario when securing applications and guides you through the best policy assertion choices for your selected applications.
• Web services hosted by ASP.NET (also known as ASMX web services) can now be hosted outside of IIS, such as in console applications or Windows services, and invoked using the TCP/IP protocol. Existing lightweight, message-oriented SOAP programming models based on the SoapSender and SoapReceiver classes can still serve as alternative messaging APIs.
WSE has been replaced by Windows Communication Foundation (WCF).
WSE stopped receiving updates because . NET Framework 2.0 is supported by the latest version (WSE 3.0) (its support was discontinued on July 12, 2011). WCF provides equivalent functionality.
|
Posted on 4/15/2020 11:32:33 AM
|
|
|
