[OASIS Issue Tracker] (EBXMLMSG-58) Use of WS-Security timestamp element

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/EBXMLMSG-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sander Fieten updated EBXMLMSG-58:
----------------------------------

    Proposal: 
Add another profiling rule (b) to section 5.1.3 of the AS4 profile stating:
"When using a WS-Security header a sending MSH MAY insert a wsu:Timestamp element in this header. A receiving MSH MUST NOT reject messages for lacking a wsu:Timestamp element, i.e. it MUST NOT generate an error with severity FAILURE."

  was:
Add another profiling rule (b) to section 5.1.3 of the AS4 profile stating:
"When using a WS-Security header a sending MSH MAY insert a wsu:Timestamp element in this header. A receiving MSH MUST NOT reject messages for lacking a wsu:Timestamp element."


> 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)