List of Figures

Chapter 1: Presenting Web Services

Figure 1-1: Business case for Web Services transaction

Figure 1-2: Company A retrieves WSDL data for company B’s Web Service

Figure 1-3: Company A sends a SOAP message to company B

Chapter 2: Presenting Security

Figure 2-1: PKI used for Web Services

Chapter 3: New Challenges and New Threats

Figure 3-1: Security based on the end user of a Web Service

Figure 3-2: The ASP.NET Add New File page

Figure 3-3: ASP.NET development environment

Figure 3-4: The ASP.NET Web Services deployment dialog box

Figure 3-5: Direct vs. indirect access to a Web Service

Figure 3-6: Multiple security contexts

Figure 3-7: Multiple Security Contents when SOAP is routed

Chapter 6: SAML

Figure 6-1: Portable trust authentication

Figure 6-2: Interdomain authentication issues

Figure 6-3: Centralized interdomain authentication issues

Chapter 7: XACML

Figure 7-1: XACML architectural diagram

Chapter 9: WS-Security

Figure 9.1: IBM and Microsoft Web Services security specifications

Chapter 10: .NET and Passport

Figure 10-1: Kerberos ticket distribution

Figure 10-2: Secret key exchange occurs out of band

Figure 10-3: User authentication to a Passport partner server

Figure 10-4: Viewing assemblies with the .NET Framework Configuration console

Figure 10-5: Creating a new permission set with the .NET MMC

Figure 10-6: Assigning security permissions to an assembly

Figure 10-7: Remove every unused ISAPI filter

Chapter 11: The Liberty Alliance Project

Figure 11-1: Joan (the Principal) is authenticated by IDP1 (her identity provider) when she browses to her personalized BigWebRetailer (her service provider) Web page

Chapter 12: UDDI and Security

Figure 12-1: UDDI data structures and service types

Figure 12-2: Inserting a new businessEntity record into the IBM test registry

Figure 12-3: Inserting a new tModel record into the IBM test registry

Chapter 14: Legal Considerations

Figure 14-1: Security in the message

Figure 14-2: SAML assertions in action

Appendix: Case Studies

Figure A-1: The Security Management Wizard in VordelSecure

Figure A-2: Loading a Web Service description in VordelSecure

Figure A-3: Basing a security policy on a preexisting policy

Figure A-4: Integrity filter, using XML Signature

Figure A-5: XML Schema enforcement

Figure A-6: Configuring message-based authentication

Figure A-7: Routing successful messages from the XML gateway to an internal Web Service

Figure A-8: Configuring alert conditions in VordelSecure