OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (EBXMLMSG-101) AS4 5.1.4/5.1.4 which message parts to sign


Pim van der Eijk created EBXMLMSG-101:
-----------------------------------------

             Summary: AS4 5.1.4/5.1.4 which message parts to sign
                 Key: EBXMLMSG-101
                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-101
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Bug
          Components: AS4 Profile
            Reporter: Pim van der Eijk


AS4 5.1.4 (b) states:

AS4 MSH implementations are REQUIRED to include the entire eb:Messaging SOAP header block and the (possibly empty) SOAP Body in the signature. 

AS4 5.1.5 (b) states that:

AS4 MSH implementations are REQUIRED to include the entire eb:Messaging header block and all MIME body parts of included payloads in the signature.

The phrase "all MIME body parts" apparently intends to reference to SOAP Body and all MIME parts but this is not clear. It seems to have confused one vendor in not signing the body with SWA. 






--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]