Web Services Training Overview|
This advanced course introduces Java developers to key concepts and technology for developing secure web services and securing enterprise software architecture. Though consensus is forming, and standards have largely taken shape, this is still a broad and challenging field. We focus on a few well-defined approaches: XML cryptography, the WS-Security and WS-SecurityPolicy standards, and the Security Assertions Markup Language, or SAML. We also look XACML for authorization policies, and at trust and federation -- not only as envisioned by SAML but also through the WS-Trust and WS-Federation specifications.
These approaches do overlap, and through our primary case studies we present a single, coherent story of assuring confidentiality, integrity and non-repudiation, user authenticity, and proper request authorization with a blend of policy-driven WS-Security, SAML, and even some application-coded digital signature. We also investigate the web-application end of SAML, with an in-depth study of single sign-on and federated identity.
Although for practical purposes this course relies on a specific platform, which is Java EE, the great majority of the course content teaches interoperable specifications, and would be equally useful to developers working on other web-service-capable platforms such as .NET -- or to those who work with multiple platforms, and do need to understand the interoperable pieces in detail but perhaps don't need to delve into implementation strategies. In fact, customizations are available that essentially leave out the Java to stick more strictly to the XML.
Web Services Training Prerequisites
Web Services Training Learning Objectives
- Solid Java programming experience is essential; Course "Java Programming" provides excellent preparation.
- Experience developing Java Web services is likewise a hard requirement: labs will assume understanding of both SAAJ and JAX-WS. Course "Developing Java Web services" is strongly recommended.
- Students are expected to be able to read and write XML fluently, and have some familiarity with XML Schema.
After completing this course, the student should be able to:
Web Services Training Course duration
- Understand the unique challenges in securing interoperable XML-based services.
- Apply W3C standards to digitally sign and encrypt XML fragments and documents.
- Understand the importance of the WS-Security specifications to interoperably secure messaging.
- Use state-of-the-art tools to configure or implement signature, encryption, and various WS-Security header content for Java web services.
- Drive such WSS implementations from WS-SecurityPolicy documents.
- "Vouch for" a user across domains to achieve request authorization without sharing credentials.
- Exchange security information between servers, applications, and components, using SAML assertion and protocol models.
- Understand the role of XACML in policy management and decision-making.
- Understand the WS-Trust and WS-Federation architectures for developing the trust relationships that enable service federations and service-oriented architectures.
- Build web applications that participate in SAML federation and single sign-on.
Web Services Training Course outline
Chapter 1. Securing the Service-Oriented Enterprise
Chapter 2. Transport Security
- Security for Web Services
- CIA Goals
- Solution Levels: W3C, OASIS, Java EE
- Scenario: Secure Multi-Party Conversation
- WS-Security and WS-SecurityPolicy
- Scenario: Sharing Security Information
- SAML and XACML
- Scenario: Multiple User Realms
- Scenario: Single Sign-On
- Technology Stacks: WS-Federation and Liberty Alliance
- The WS-I Basic Security Profile
Chapter 3. XML Signature
- Use Case: Secure Transport
- HTTP Authentication Schemes
- HTTP BASIC
- HTTP DIGEST
- Securing Web-Service URLs
- JAX-WS Support
- Axis Support
Chapter 4. XML Encryption
- Use Case: Non-Repudiation
- XML Digital Signature
- Cryptography Backgrounder
- Canonical XML
- Enveloped, Enveloping, and Detached Signatures
- SignedInfo and References
- The Java Cryptography Architecture
- Why Keys Aren't Enough
- X.509 Certificates and Certificate Chains
- The KeyStore API
- Java XML Digital Signature API
- Steps to Sign and Verify XML Content
- JAX-WS Message Handlers
- Foiling the Man in the Middle
Chapter 5. WS-Security
- Use Case: Confidentiality
- XML Encryption
- Element vs. Content Encryption
- Key Wrapping
- The Java Cryptography Extensions
- Apache XML Security
- Steps to Encrypt and Decrypt XML Content
- Choosing Algorithms and Key Sizes
Chapter 6. WS-SecurityPolicy
- Use Case: Secure Message Exchange
- Use Case: User Login
- The WS-Security Specifications
- Security Token Types
- Username Tokens
- Signature and Encryption
- Tools for WS-Security
- XWSS and JAAS
- Foiling Replay Attacks
Chapter 7. Introduction to SAML
- Use Case: Sharing Metadata
- Normalized vs. Compact Form
- Policy Attachment
- Policy Scopes
- Protection Assertions
- Token Assertions
- Supporting and Endorsing Tokens
- Metro and WSIT
- Implementing Callbacks
- Integrating Security Frameworks
Chapter 8. SAML Assertions
- History of SAML
- Using OpenSAML
- SAML and Web Services
Chapter 9. SAML Protocol
- Use Case: "Vouching for" a User
- The Assertions Schema
- Assertions and Subjects
- NameID Types
- Subject Confirmation
- Confirmation Methods
- Authentication Contexts
- Attribute Profiles
- Actions and Evidence
- WS-Security and SAML Tokens
- OpenSAML Assertions Model
- Creating XML Objects
- Marshalling and Unmarshalling
Chapter 10. XACML
- Use Case: Back-Channel Queries
- Requests, Queries, and Responses
- Status and StatusCode
- Other Request and Response Types
- OpenSAML Protocol Model
- SAML and XML Signature
- SAML and XML Encryption
Chapter 11. Securing Federated Services
- Use Case: Back-Channel Authorization
- Use Case: Sharing Authorization Policies
- Policies, Policy Sets, and Targets
- Combining Algorithms
- Policy Context
- Request and Response Types
- The SAML Profile of XACML
- Authorization Decisions via XACML
Chapter 12. SAML Bindings
- Publish, Find, Bind ... Execute!
- The Trust Problem
- The Security Token Service
- Messaging Model: RST and RSTR
- Derived Keys
- Secure Conversation Metrics
- Value Proposition
Chapter 13. Federated Identity
- Use Case: Speaking "Through" the Browser
- The SOAP Binding
- SAML Over HTTP
- The Browser as Messenger
- The Redirect, POST, and Artifact Bindings
- The PAOS Binding
- The URI Binding
Appendix A. Learning Resources
- What is Federation?
- Problems for Identity Federation
- SAML 2.0 Federations
- Single Sign-On
- Account Linking and Persistent Pseudonyms
- Transient Pseudonyms
- Name ID Mapping
- Federation Termination
Appendix B. Web-Service Security Prefixes and Namespaces
Minimum Hardware Requirements
- 1.5 GHz, 1 gig RAM, 2 gig disk space.
Hardware – recommended
- All free downloadable tools
Network and Security
- 2 GHz, 2 gig RAM, 3 gig disk space
- An internet connection is required for each student and instructor machine. Limited privileges required
- Tested on Windows XP Professional. Course software should be viable on all systems which support the Java EE 5.0 SDK.