[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (EBXMLMSG-15) D3.4 Pmodes for error handling
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pim van der Eijk updated EBXMLMSG-15:
-------------------------------------
No extra state is needed since we all need to record whether signing is used or not for receipt, that information would apply to errors as well.
> D3.4 Pmodes for error handling
> ------------------------------
>
> Key: EBXMLMSG-15
> URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-15
> Project: OASIS ebXML Messaging Services TC
> Issue Type: Improvement
> Components: Core Spec
> Reporter: Pim van der Eijk
>
> There does not seem to be a way to specify that ebMS3 error messages are to be signed or encrypted. The parameters in D3.5 are about the business message. In particular for asynchronous errors, it is useful to be able to authenticate the MSH that is posting this error to validate it is the MSH to which the message in error was sent and not some other.
> For AS4 we could simplify this and state that an asynchronous error on a message should be signed if and only if the message in error was signed, as we did with receipt.
--
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]