[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBXMLMSG-58) Use of WS-Security timestamp element
[ https://issues.oasis-open.org/browse/EBXMLMSG-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42040#comment-42040 ] Pim van der Eijk commented on EBXMLMSG-58: ------------------------------------------ For now, TC considers this implementation dependent. Sending MSH MAY include wsu:Timestamp Receiving MSH MUST NOT reject messages for lacking a wsu:Timestamp. > Use of WS-Security timestamp element > ------------------------------------ > > Key: EBXMLMSG-58 > URL: https://issues.oasis-open.org/browse/EBXMLMSG-58 > Project: OASIS ebXML Messaging Services TC > Issue Type: Improvement > Components: AS4 Profile, Core Spec > Reporter: Pim van der Eijk > > We currently do not specify the use of WS-Security timestamps. > In interop testing it turned out that one product uses it for duplicate elimination and expected it to be set. > Should we clarify that the element is not required, or add a PMode parameter to have it configurable? -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]