[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Short List of SwA Inteorp 1 Issues
All, There were two main issues that we encountered during the first interoperability event for SwA. There were others, but these were corrected with fixes to the scenarios document and mostly resulted from typos. 1. The SwA Interop Scenarios push Base 64 encoding and decoding to the MIME layer. That is, encrypted attachments use a Content-Type of "base64". This means that implementations should not add a base 64 decoding as a <Transform> in the <CipherReference> element. 2. Implementations should take care when forming SwA message packages. For example, the main payload for a SOAP message package begins with the boundary name. The initial Content-Type header is an HTTP header and not part of the main SOAP payload. I am attaching the latest interop scenarios document as well as the collated results provided by Maneesh from Actional. Kind Regards, Blake Dournaee Senior Security Architect http://www.sarvega.com Sarvega, Inc.ÿþ<