[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: WSS 1.1 Interop report
Here is the interop report for the recent OASIS WSS 1.1 Interop event. 4 parties participated. Interop was achieved between all 4 parties. The following issues arose; 1. Lines 1713-1741 (Section 9.4.4) define processing rules for wsse11:EncryptedHeader. During interop testing it was identified that some implementations expected wsse11:EncryptedHeader/xenc:EncryptedData/@Type to be present while other implementations did not emit such an attribute. Given that neither #Element nor #Content match the semantics of wsse11:EncryptedHeader we propose that the following text be added to section 9.4.4; "wsse11:EncryptedHeader/xenc:EncryptedData elements SHOULD NOT carry a Type attribute. Implementations MUST process wsse11:EncryptedHeader/xenc:EncryptedData elements in the absence of a Type attribute" Note: 3 of the 4 parties to the interop support the above proposal. 2. Lines 986-987 - The parenthetical statement implies that the base value for EncodingType defined in the following table is http://docs.oasisopen.org/wss/2005/xx/oasis-2005xx-wss-soap-message-secu rity-1.1#Base64Binary and we believe it should be http://docs.oasisopen.org/wss/2004/01/oasis-200401-wss-soap-message-secu rity-1.0#Base64Binary. This caused some problems at the interop as some implementations used the former URI and some the latter.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]