1. T-110.455 Network Application Frameworks and XML Summary and Conclusions 27.04.2005 Sasu Tarkoma

2. Topics Covered n Distributed systems security n Multi-addressing: Mobility and multi- homing n Building applications with XML u Distributed objects u Role of directory services u Mobile and wireless applications u XML-based presentation and RPC n Scalability and performance issues

3. Lecture Outline Note: starts 16.00

4. Interconnections n Interconnections applicable on many levels u Network-level operation F DNS, overlay lookup, IPsec u Application-level operation F UDDI, SSL, WS-Security NetworkSecurity Directories Objects

5. Mobility and Routing

6. Naming, Addressing, and Routing NAMING ADDRESSING ROUTING How to identify and name a node? Frequent updates? One or two new name spaces? Where is the node located? Differences (IPv4/IPv6) Multi-addressing? How to route information to the node’s address? NAT traversal? Overlay vs. network routing unicast: to a specific node broadcast: to all nodes multicast: to a subset of nodes anycast: to any one in some subset (IPv6)

7. TCP/IP Network Stack Networking Layer (IP) Transport Layer (TCP/UDP) Application Layer Underlying network (link layer) host-to-host transport reliability, congestion control, flow control host-to-host connectivity routing, addressing Link layer: local data transfer, encoding, framing, error correction Physical: transmission of signals All applications (FTP, Telnet, HTTP, Overlays) HOST-TO-HOST

8. Routing vs. mobility n Topology data aggregation is necessary u Cannot track all hosts in the world u IP addresses determined by topology F Network gives the routing prefix n Mobile hosts must change their IP addresses u Causes sockets / connections to break n How to communicate address changes? n Goal of a mobility protocol u Transport and applications do not see address changes

9. Networks: Mobility R Public Switched Data Network Router R RR R Backbone LAN Router MAN NAT AP GPRS/UMTS Access network NAT BS MH Ad hoc MH

10. Rendezvous n How to find the moving end-point? u Tackling double jump F What if both hosts move at the same time? F Requires a rendezvous point n Mobility management is needed! u Initial rendezvous u Can be based on directories u Requires fast updates to directories F Does not work well for DNS

11. Identity/Locator split Process Transport ID Layer IP Layer Link Layer identifier locator n New name space for IDs u Maybe based on DNS u Maybe a separate namespace u Maybe IP addresses are used for location u Good for hiding IP versions n Communication end- points (sockets) bound to identifiers

12. Host Identity Protocol n New cryptographic namespace n Connection endpoints mapped to 128 bit host identity tags (hashes of public keys) n Mapping at HIP layer n 4-phase Base Exchange with cryptographic puzzle for DoS prevention n IPSec for network-level security

13. Upper layer view n IP connectivity problematic today u Broken by firewalls, NATs, mobility u Two versions of IP: IPv4 and IPv6 n HIP has a potential remedy u Restores end-to-end connectivity (NAT traversal possible but may require changes / tunnelling) u Adds opportunistic security u Handles mobility and multi-homing u Requires DHT based overlay (currently missing) n Where is the network state? u Routers know addresses F Like today u DHT knows HITs / SIDs F Lease based storage u Middleboxes know SPIs F Soft state

14. Lessons to learn n Hierarchical routing likely to stay u Addresses carry topological information u Efficient and well established n Applications face changing connectivity u QoS varies u periods of non-connectivity n Identifiers and locators likely to split n Mobility management is needed n Probably changes in directory services u Overlays have been proposed

15. Summary n Topology based routing is necessary n Mobility causes address changes n Address changes must be signalled end- to-end n Mobility management needed u Initial rendezvous: maybe a directory service u Double jump problem: rendezvous needed n Many engineering trade-offs

16. Distributed Hash Tables and Overlays

17. Layered-model revisited Object API Firewall bypass End-to-end Routing Congestion control Presentation DNS names IP addresses Routing paths XML presentation Finding, meta-data, invoking, syncing, mobility. Web Services

18. Overlay Networks n Origin in Peer-to-Peer (P2P) n Builds upon Distributed Hash Tables (DHTs) n Easy to deploy u No changes to routers or TCP/IP stack u Typically on application layer n Overlay properties u Resilience u Fault-tolerance u Scalability

19. Upper layers Overlay Congestion End-to-end Routing DNS names, custom identifiers Overlay addresses IP addresses Routing paths

20. Some DHT applications n File sharing n Web caching n Censor-resistant data storage n Event notification n Naming systems n Query and indexing n Communication primitives n Backup storage n Web archive

21. Applications for DHTs n DHTs are used as a basic building block for an application-level infrastructure u Internet Indirection Infrastructure (i3) F New forwarding infrastructure based on Chord u DOA (Delegation Oriented Architecture) F New naming and addressing infrastructure based on overlays

22. Summary n Mobility and multi-homing require directories u Scalability, low-latency updates n Overlay networks have been proposed u Searching, storing, routing, notification,.. u Lookup (Chord, Tapestry, Pastry), coordination primitives (i3), middlebox support (DOA) u Logarithmic scalability, decentralised,… n Host/identity split and overlays for directories seem good candidates for solving many of the issues with mobility and multi-homing

23. Middleware

24. n Widely used and popular term n Fuzzy term n One definition u “A set of service elements above the operating system and the communications stack” n Second definition u “Software that provides a programming model above the basic building blocks of processes and message passing” (Colouris, Dollimore, Kindberg, 2001)

25. Why Middleware? n Application development is complex and time-consuming u Should every developer code their own protocols for directories, transactions,..? u How to cope with heterogeneous environments? F Networks, operating systems, hardware, programming languages n Middleware is needed u To cut down development time F Rapid application development u Simplify the development of applications u Support heterogeneous environments and mask differences in OS/languages/hardware

26. Middleware cont. n Middleware services include u directory, trading, brokering u remote invocation (RPC) facilities u transactions u persistent repositories u location and failure transparency u messaging u Security n Network stack (transport and below) is not part of middleware

27. Transparencies n Location transparency u RPC and RMI used without knowledge of the location of the invoked procedure / object n transport protocol transparency u RPC may be implemented using any transport protocol n transparency of OS and hardware u RPC/RMI uses external data representation u Presentation is important u XML is becoming increasingly important n transparency of programming languages u language independent definition of procedures: CORBA IDL

28. Network Application Framework n Network Application Framework is middleware n Contains services for distributed applications n Middleware as a term is fuzzier and larger n In this course, we focus on network application frameworks and XML u objects (discovery, representation) u directories (overlays,..) u network u security

29. Examples n Middleware u CORBA u Message-oriented Middleware u Event Systems & tuple spaces u Java Message Service u Java 2 Enterprise Edition (J2EE) u.NET n Mobile middleware u WAE u J2ME u Wireless CORBA u FUEGO

30. Mobile Middleware I n Middleware is typically designed and implemented for fixed-network hosts u High bandwidth, low latency, reliable communication u Persistent storage and sufficient computing power u No mobility n Mobile environment requires new solutions u Existing middleware services do not scale u Previous lectures: mobility is challenging u Small devices / embedded systems pose totally different challenges

31. Mobile Middleware II n Goals for middleware: u fault-tolerance, adaptability, heterogeneity,scalability, resource sharing n Mobile middleware u dynamically changing context u decoupled F events, tuple spaces u Basic solution for wireless F Use a proxy

32. Summary n Middleware u for application development and deployment u for supporting heterogeneous environments u Main communication paradigms: RPC/RMI, asynchronous events (publish/subscribe) u J2EE, CORBA,.. n Mobile middleware u Desktop middleware not usable on small, mobile devices u Special solutions are needed u J2ME, Wireless CORBA,..

33. Web Services

34. A Basic Web Service Computer A Language: C++ OS: W2000 Computer A Language: C++ OS: W2000 Computer B Language: Java OS: Linux Computer B Language: Java OS: Linux XML Independent of language, OS, network protocols

35. Standardization n W3C Web Services u XML Protocol Working Group F SOAP u Web Services Addressing Working Group u Web Services Choreography Working Group u Web Services Description Working Group F WSDL n OASIS u E-business standards, UDDI n WS-I (Web Service Interoperability Org.) u Binding profiles,..

36. Web Service Architecture n The three major roles in web services u Service provider F Provider of the WS u Service Requestor F Any consumer / client u Service Registry F logically centralized directory of services n A protocol stack is needed to support these roles

37. Web Services Protocol Stack n Message Transport u Responsible for transporting messages u HTTP, BEEP n XML Messaging u Responsible for encoding messages in common XML format u XML-RPC, SOAP n Service Description u Responsible for describing an interface to a specific web service u WSDL n Service discovery u Responsible for service discovery and search u UDDI

38. WS Protocol Stack Transport: HTTP, FTP, BEEP, SMTP, JMS XML Messaging: SOAP, XML-RPC, XML Description: WSDL Discovery: UDDI

39. WSDL with Java Services WSDL document JAXR UDDI Publish firewall WS requester Business partner or other system SOAP RQ Bind SOAP RQ 1. WSDL is published to UDDI 2. Look up WS 3. Retrieve WSDL description 4. Call WS JAXR= Java API for XML Registries

40. What is WSDL? n WSDL: Web Service Description Language n An XML language used to describe and locate web services u location of web service u methods that are available u data type information and XML messages n Commonly used to describe SOAP-based services n W3C standard (work in progress) u Initial input: WSDL 1.1 as W3C Note u Current version 2.0 (last call) u Some differences between 1.1 and 2.0 n WSDL 1.1 in WS-I Basic Profile 1.0 and 1.1.

41. WSDL Overview : ROOT WSDL element : The data types that are used : What messages are transmitted? : The supported operations : The binding to concrete protocols : Reference to actual location

42. 42 of 20 Mapping SOAP to WSDL

43. Putting it together Source: http://msdn.microsoft.com/

44. 44 of 20 SOAP Message Structure SOAP Envelope SOAP Header Header block SOAP Body Message Body Optional header contains blocks of information regarding how to process the message: u Routing and delivery settings u Authentication/authorizatio n assertions u Transaction contexts n Body is a mandatory element and contains the actual message to be delivered and processed (and fault information)

45. 45 of 20 What is UDDI? n Universal Description Discovery and Integration n Industry-wide initiative supporting web services n Specifications u Schemas for service description u Schemas for business (service implementers) description u Developed on industry standards F Applies equally to XML and non-XML web services n Implementation u Public web service registry and development resources u SOAP-based programming protocol for registering and discovering Web services F XML schema for SOAP messages F a description of the API n UDDI does not directly specify how pricing, deadlines, etc. are handled/matched u Advanced discovery via portals and marketplaces

46. Web Services Security

47. Need for XML security n XML document can be encrypted using SSL or IPSec u this cannot handle the different parts of the document u documents may be routed hop-by-hop u different entities must process different parts of the document n SSL/TLS/IPSec provide message integrity and privacy only when the message is in transit n We also need to encrypt and authenticate the document in arbitrary sequences and to involve multiple parties

48. High-level view to WS security n Security is as strong as the weakest link n The options for an attacker are: u Attack the Web Service directly F Using ”unexpected” XML u Attack the Web Services platform u Attack a WS security tool u Attack the underlying operating system or network connection

49. Application-layer Security n Identity-based security u Authentication and authorization information shared across security domains n Content-based security u Protecting against buffer overflow and CGI-like attacks u Must have knowledge about the applications to which these messages are directed n Accountability or non-repudation u Need message level security u Maintain integrity, archived audit trails n The standards and specifications mentioned earlier address these issues

50. Standardization landscape n Who are specifying the basic standards? n Who are specifying the higher level standards? n Who is implementing the standards?

51. Who are specifying the standards? n Joint IETF/W3C u XML Signature (www.w3.org/Signature)www.w3.org/Signature n W3C u XML Encryption (www.w3.org/Encryption/2001)www.w3.org/Encryption/2001 u XML Key Management (XKMS) (www.w3.org/2001/XKMS)www.w3.org/2001/XKMS n OASIS u WS-Security F SOAP Message Security specification etc. u SAML: Security Assertion Markup Language u XACML: Extensible Access Control Markup language u Electronic Business XML (ebXML) (with UN/CEFACT) n Web Services Interoperability Organization (WS-I) u Basic security

52. Standardization Groups XML Encryption XML Signature XKMS XrML WS-Security Provisioning Biometrics XACML SAML W3COASIS Security Assertion Markup language XML Common Biometric Format (XCBF) Extensible Rights Markup Language eXtensible Access Control Markup Language (XACML) XML Key Management Specification

53. Basic XML Security n XML Digital Signatures (XMLDSIG) n XML Encryption n XML Canonicalization n XML Key Management

54. Digital Signatures Message Digest Message Digest Message Private keyPublic key Asymmetric Key Pair SIGNVERIFY Signature Pass/Fail Need to know the message, digest, and algorithm (f.e. SHA1)

55. XML Digital Signatures (cont.) ( ( )? )+ ( )? ( )*

56. Encryption Public keyPrivate key Asymmetric Key Pair EncryptDecrypt

57. XML Encryption ? ? ? ?

58. Why Canonicalization is Hard n Exactly the same sequence of data bytes must be used for signing as for verifying u Problem of DTDs & Schemas u Problem of white space u Curse of namespaces u The usual: F Encodings & character sets (UTF-8,..) F Representations (, ) F Reordering of attributes

59. XML Key Management (XKMS) n A Web Service that provides an interface to a PKI u Abstracts PKI certificates u Towards centralized PKI management (an enterprise resource vs. configured by end-clients) n Designed to manage the sharing of public keys u Managing includes verifying signatures u Also includes encrypting messages n XKMS takes complexity from the applications n Originally from u VeriSign, Microsoft, webMethods n XKMS 1.0 u W3C Note 30 March 2001 n XKMS 2.0 u W3C Candidate Recommendation 5 April 2004

60. XML Key Management (XKMS) n The XML Key Management Specification (XKMS) comprises two parts u the XML Key Information Service Specification (X-KISS), and F Retrieval of information about keys u the XML Key Registration Service Specification (X-KRSS). F Store of information about keys n Uses the SOAP 1.1 protocol for communication, XML Schema, WSDL 1.0 n Based on XML Signatures

61. Web Services Security Requirements n Access control to Web services u WS-Security, XML-Signature u SAML – Issuing and validation of SAML assertions u Digital certificate validation n Content-filtering XML u Filters based on data format (XSD) u Filters based on content (XPath) u Filters based on integrity (XML Signature)

62. Functional point of view Routing IntegrityValidation Content Checking Authentication Authorization XML Management Console Design and Deploy Security policies ID Management LDAP PKI Single Sign-On Reporting Activity Alerting Secure logging XML

63. Security Contexts in Web Services n Remember Web Services goals: u Re-use existing services u Combine services from several domains n Security result: Must support several security domains u SOAP intermediaries u Reusing security tokens from one message in another message

64. WS Security I n Web Services Security: SOAP Message Security 1.0 (Oasis Standard 2004) n End-to-End security u Headers are decrypted and processed as needed n Selective processing u Some parts are plain text u Some are encrypted u Some are signed n How does it work? u SOAP header carries security information (and other info as well)

65. WS Security II n Ability to send security tokens as part of a message, message integrity, and message confidentiality n Security model in terms of security tokens combined with digital signatures to protect and authenticate SOAP messages n An X.509 is an example of a signed security token endorsed by a CA. n When third party support is not available, receiver may choose to accept the claims in the token based on trust on the entity that sent the message.

66. SAML n SAML (Security Assertion Markup Language) u A XML-based framework (schemas) for the exchange of authentication and authorization information u A standard message exchange protocol F How you ask and receive information n Mainly for integration, up to relying parties to decide to what authentication authority to trust n Assertions can convey information about authentication acts performed by subjects, attributes of subjects, and authorization decisions about whether subjects are allowed to access certain resources u Authentication statements merely describe acts of authentication that happened previously n Specified by OASIS

67. SAML in a nutshell n XML-based framework for exchanging security information u XML-encoded security assertions u XML-encoded request/response protocol u Rules on using assertions with standard transport and messaging frameworks n SAML & WS-Security allow a SOAP message to include information about the end-user’s authentication status

68. Summary n Security contexts u Security needed within and between contexts u XML validation, encryption, and authentication needed between security contexts! n WS security standard revisited u SOAP header carries security information (and other info as well) u Selective processing n SAML u Statements about authorization, authentication, attributes u SAML & WS-Security & XACML n Implementations available

69. Putting it together

70. With identity/locator split + overlays? Upper layers Overlay Congestion End-to-end Routing Overlay addresses IP addresses Routing paths DNS names, custom identifiers Host Identities IP addresses Routing paths ID Layer CONTROL DATA

71. ”Theory” WS Security SOAP TCP IP ”Practice” WS Security SOAP TCP4 IPv4 HTTP/TLS/sockets TCP6 IPv6 ”Future?” WS Security SOAP IPv4 HTTP?/sockets IPv6 TCP HIPsec HIPCTRLHIPCTRL HIPCTRLHIPCTRL

72. Discussion

73. Important Dates n Exam on Thursday 12.5. 12-15 in T1. n Deadline for the second assignment 15.5.