100 likes | 120 Views
Learn to enhance web services security using WSE 2.0 with features like WS-Security, Secure SOAP Messages, WS-SecurityPolicy, and more. Understand WSE architecture and policies for securing and routing SOAP messages.
E N D
Secure Web ServicesDevelopment with Microsoft Web Services Enhancements (WSE 2.0) Jim Van Dyke
WSE 2.0 • Add-on to Visual Studio .NET and the .NET Framework • Interface Tool and Classes that implement the WS-* Specifications
WS-* Specifications • WS-Security • Secure SOAP Messages; Confidentiality (encryption) and Integrity (digital signatures) • WS-SecureConversation • Secure Communications; Security Contexts
WS-* Specifications • WS-Policy and WS-SecurityPolicy • Means to specify security policies and requirements (e.g., security token requirements) • WS-Trust • Means to exchange security tokens; Communications protocol for federation • WS-Federation • Brokering Trust, Single Sign-in/out, Attributes, and Pseudonyms
WSE: Major Features • Securing Web services • Security credentials, Digital signing, Encryption • Policy • SOAP messaging • Routing SOAP messages • Sending attachments with SOAP messages
WSE Architecture • WSE filter chains are integrated with the SOAP Messaging built-into WSE and the ASP.NET Web services infrastructure.
WSE Policies • There are four basic steps to configure a Web service's policy: • Create a policy file. • Declare the set of policies for the policy file. • Map the policies to SOAP endpoints. • Configure the policy file.
WSE Policies • WSE has built-in support the following policy assertions: • Security token • Integrity • Confidentiality • Message age • Message predicate
Basic FederationDirect Trust Token Exchange IP/STS IP/STS Trust Get identity token Get accesstoken 1 2 Resource Requestor 3 Partially adapted from workshop slides by Tony Nadalin (IBM) and Chris Kaler (Microsoft)