2005/08/31ACS WG - Data transport with SOAP message 1 Data transport with SOAP message There is a W3C note proposing the SOAP with attachment: –

2005/08/31ACS WG - Data transport with SOAP message 2 OASIS WSS TC SOAP Messages with Attachments (SwA) Profile 1.1 –OASIS Public Review Draft 01, 28 June 2005 is being discussed in the OASIS Web Services Security TC. –This document describes how to use the OASIS Web Services Security: SOAP Message Security standard [WSS-Sec] with SOAP Messages with Attachments [SwA]. More specifically, it describes how a web service consumer can secure SOAP attachments using SOAP Message Security for attachment integrity, confidentiality and origin authentication, and how a receiver may process such a message. – 01.htmlhttp:// 01.html

2005/08/31ACS WG - Data transport with SOAP message 3 WS-I Attachments Profile 1.0 ( refers this as below:Attachments Profile 1.0 ( –SOAP Messages with Attachments (SwA) defines a MIME multipart/related structure for packaging attachments with SOAP messages. This profile complements the Basic Profile 1.1 to add support for conveying interoperable SwA-based attachments with SOAP messages. –Attachments Profile 1.0 is referred from WS-I Basic Profile 1.1 ( Basic Profile 1.1 (

2005/08/31ACS WG - Data transport with SOAP message 4 Some other specifications. Relevant specifications for data transport with SOAP. –SOAP 1.2 Attachment Feature –SOAP Message Transmission Optimization Mechanism

2005/08/31ACS WG - Data transport with SOAP message 5 Other Information on the Web Overview - SOAP Attachments - SOAP Attachments SAAJ: SOAP Attachment API for Java SOAP Attachment API for Java SOAP 1.2, Introduction 1.2, Introduction Web Services Support over J2EE Services Support over J2EE Java Web Services Developer Pack dfJava Web Services Developer Pack df –SOAP with Attachments API for Java (SAAJ) 1.2SOAP with Attachments API for Java (SAAJ) 1.2

2005/08/31ACS WG - Data transport with SOAP message 6 SOAP message and MIME A SOAP message with MIME header. MIME-Version: 1.0 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: Content-Location: claim061400a.xml <SOAP-ENV:Envelope xmlns:SOAP-ENV=" SOAP message

2005/08/31ACS WG - Data transport with SOAP message 7 SOAP message with attachment(1) A SOAP message with attachment can be stored in a multipart MIME structure. –The SOAP message itself will be stored in the “root” body part* of the multipart MIME structure. –Attachments to the SOAP will be stored in other parts in a multipart MIME structure. The SOAP message will contain reference to the attachment. –See examples in following pages. SwA proposes how the reference for the parts in MIME is resolved. See the quotes from the SwA doc to be more precise. An ACS request as a SOAP message can be contained in the “root” body part of the Multipart/Related MIME structure and has a reference to the attachments, if there are any. * RFC 2387 specifies that “root” body part can be indicated with “start” attribute in the Content-Type header and the first one in the parts by default.

2005/08/31ACS WG - Data transport with SOAP message 8 SOAP message with attachment(2) RFC 2396 specifies a process skeleton for establishing a base URI, based on the following options, listed in order of precedence. 1.Base URI within Document Content: the mechanism for explicit specification of a base URI within a SOAP 1.1 message will be the XML base mechanism. 2.Base URI from an Encapsulating Entity: If there is a Content-Location header containing an absolute URI in any MIME entity enclosing the primary SOAP 1.1 message, then the URI from the closest such Content-Location header is the base URI for the entity. 3.Base URI from the Retrieval URI: the retrieval URI for a SOAP message package is never allowed to be used as a base URI. 4.Default Base URI: the default base URI will be "thismessage:/" in accordance with RFC SwA proposes how the reference for the parts in MIME is resolved. –Every MIME part in the Multipart/Related structure that constitutes a SOAP message package has at least one absolute URI label. There are three cases. 1.If a Content-Location header is present with an absolute URI value then that URI is a label for the part. 2.If a Content-Location header is present with a relative URI value then rules 2 and 4 above are applied to establish the base URI for the process of converting the relative URI to an absolute one. The resulting absolute URI is a label for the part. 3.If a Content-ID header is present, then an absolute URI label for the part is formed using the CID URI scheme as described in RFC 2111.

2005/08/31ACS WG - Data transport with SOAP message 9 SOAP message with attachment(3) MIME-Version: 1.0 Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml; start=" " Content-Description: This is the optional message description. Content-Location: --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: Content-Location: claim061400a.xml <SOAP-ENV:Envelope xmlns:SOAP-ENV=" --MIME_boundary Content-Type: image/tiff Content-Transfer-Encoding: base64 Content-Location: claim061400a.tiff...base64-encoded TIFF data... --MIME_boundary-- SOAP message Attachment to the SOAP message, as another part of the multipart MIME message referencing URI to the attachment Referenced URI Base URI

2005/08/31ACS WG - Data transport with SOAP message 10 ACS request as a SOAP message ACS requests are represented in SOAP message. ACS (ARI) Create request is accompanied with AA document. The AA document itself can be embedded in the request message or an attachment to the message.

2005/08/31ACS WG - Data transport with SOAP message 11 ACS Create message (1) Discrete files in multipart MIME: : Each refers to other parts in MIME multipart structure (or external storage).

2005/08/31ACS WG - Data transport with SOAP message 12 Discrete files in multipart MIME -Structure of the ACS Create message Create Request (SOAP) AAD AC-1 AC-2 AC-n

2005/08/31ACS WG - Data transport with SOAP message 13 ACS Create message (2) A bundled file in a MIME structure: This refers to another parts in MIME multipart structure.

2005/08/31ACS WG - Data transport with SOAP message 14 A bundled file in multipart MIME -Structure of the ACS Create message Create Request (SOAP) A bundled file containing AAD and multiple AC’s

2005/08/31ACS WG - Data transport with SOAP message 15 In summary… The AA document for ACS Create request can be embedded in the SOAP message itself without attachments, making a single XML document. Alternatively, it can be transported as SOAP with attachment. There are two possible embodiment to the attachment. –Discrete files in multiple MIME –A bundled file in a MIME