[OASIS Issue Tracker] (EBXMLMSG-43) Error EBMS:0101 description enhancement

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

    [ https://issues.oasis-open.org/browse/EBXMLMSG-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58342#comment-58342 ] 

Sander Fieten commented on EBXMLMSG-43:
---------------------------------------

The error description mentions the signature included in the WS-S header targeted to the "ebms" SOAP actor. This WS-S header however does / should not contain a signature, only the default header does. I propose to change the description as follows:

"The signature in the default Security header could not be validated by the Security module, or authentication failed due to a username token mismatch for the username token included in the Security header intended for the "ebms" SOAP actor."

> Error EBMS:0101 description enhancement
> ---------------------------------------
>
>                 Key: EBXMLMSG-43
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-43
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Theo Kramer
>            Priority: Minor
>
> ebms error code EBMS:0101 description reads as follow
> The signature in the Security header intended for the "ebms" SOAP actor, could not be validated by the Security module.
> This does not cater for the case where user tokens do not match



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)