[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (EBXMLMSG-22) Example Pull Message in spec is incorrect as it has a RefToMessageId
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34601#action_34601 ]
Sander Fieten edited comment on EBXMLMSG-22 at 9/11/13 7:44 PM:
----------------------------------------------------------------
Text of original message:
====================
ebms core 3 part 2 section 2.2.6 The One-Way/Pull MEP, states the following
i 'To conform to this MEP the pulled User Message unit MUST NOT include an eb:RefToMessageId element.'
ii however, in section 3.2 the pulled user message example does contain a 'eb:RefToMessageId' element corresponding to the pull request signal message id.
The implications of ii are as follows
o we have to add a 'eb:RefToMessageId' to the pulled user message unit
o we cannot store a signed message for queuing if we have to adjust the 'eb:RefToMessageId' as this would break the signature.
We believe that this would also be problematic in supporting multi-hop with signed messages.
PS - the above means that what I said at the last meeting that we support SOAP Security Level of sign and encrypt for a pulled user message unit with AS4 is not correct.
Comments appreciated
--
Regards
Theo
was (Author: sanderfieten):
ebms core 3 part 2 section 2.2.6 The One-Way/Pull MEP, states the following
i 'To conform to this MEP the pulled User Message unit MUST NOT include an eb:RefToMessageId element.'
ii however, in section 3.2 the pulled user message example does contain a 'eb:RefToMessageId' element corresponding to the pull request signal message id.
Text of original message:
====================
The implications of ii are as follows
o we have to add a 'eb:RefToMessageId' to the pulled user message unit
o we cannot store a signed message for queuing if we have to adjust the 'eb:RefToMessageId' as this would break the signature.
We believe that this would also be problematic in supporting multi-hop with signed messages.
PS - the above means that what I said at the last meeting that we support SOAP Security Level of sign and encrypt for a pulled user message unit with AS4 is not correct.
Comments appreciated
--
Regards
Theo
> Example Pull Message in spec is incorrect as it has a RefToMessageId
> --------------------------------------------------------------------
>
> Key: EBXMLMSG-22
> URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-22
> Project: OASIS ebXML Messaging Services TC
> Issue Type: Bug
> Reporter: Pim van der Eijk
>
> See the discussion in:
> https://lists.oasis-open.org/archives/ebxml-msg/201105/msg00033.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]