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-92) PMode[1].Security.X509.Sign in AS4

Pim van der Eijk created EBXMLMSG-92:

             Summary: PMode[1].Security.X509.Sign in AS4
                 Key: EBXMLMSG-92
                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-92
             Project: OASIS ebXML Messaging Services TC
          Issue Type: Improvement
            Reporter: Pim van der Eijk

AS4 and require support for PMode[1].Security.X509.Sign in ebHandler.

This parameter is defined in the core specification as:

The value of this parameter is a list of the names of XML elements (inside the SOAP envelope) that should be signed, as well as whether or not attachments should also be signed. The list is represented in two sublists that extend this parameter: Sign.Element[] and Sign.Attachment[]. An element within the Element[] list could be specified either by its XML name or by its qualified name (its XML name and the namespace to which it belongs). An element within the Attachment[] list is identified by the Content-Id. 

However,  AS4 sections 5.1.4 and 5.1.5 are clear about what is to be signed in an AS4 message.  So having the ability to explicitly select parts to sign is unnecessary and could lead accidental misconfiguration. 

This message was sent by Atlassian JIRA

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