Next in thread → Next in month →

[OASIS Issue Tracker] (EBXMLMSG-28) 5.1.7 State required attachment transform for encryption

From
OASIS Issues Tracker <>
Date
2018-03-20T09:40:03+00:00
ID
Thread
[OASIS Issue Tracker] (EBXMLMSG-28) 5.1.7 State required attachment transform for encryption
[ https://issues.oasis-open.org/browse/EBXMLMSG-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69316#comment-69316 ] 

Theo Kramer commented on EBXMLMSG-28:
-------------------------------------

Agreed - but suggest splitting b into b and c and re-phrasing of b

(b) AS4 MSH implementations are REQUIRED to encrypt the MIME Body parts of all included payloads. The SOAP Body  MUST be encrypted if, and only if, a payload is contained in the SOAP Body.

(c) The SOAP header including the eb:Messaging header SHALL NOT be encrypted. 

> 5.1.7 State required attachment transform for encryption
> --------------------------------------------------------
>
>                 Key: EBXMLMSG-28
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-28
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile
>            Reporter: Sander Fieten
>
> Section 5.1.7 does not mention which transforms must be supported. Similar to signing (see also issue 25) the AS4 profile should require support only for the Content-Only transform (indicated by URI : http://docs.oasis-open.org/wss/oasis-wss-SwAProfile-1.1#Attachment-Content-Only).   



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →