Uploaded image for project: 'OASIS ebXML Messaging Services TC'
  1. OASIS ebXML Messaging Services TC
  2. EBXMLMSG-101

AS4 5.1.4/5.1.4 which message parts to sign

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: AS4 Profile
    • Labels:
      None
    • Proposal:
      Hide

      Change AS4 5.1.5 (b) to:

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

      Show
      Change AS4 5.1.5 (b) to: AS4 MSH implementations are REQUIRED to include the entire eb:Messaging SOAP header block, the (possibly empty) SOAP Body and all MIME payload parts in the signature.

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              pvde Pim van der Eijk (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: