holodeck-b2b/Holodeck-B2B

Generated Content-Id can result in signature failure

sfieten opened this issue · 1 comments

The Content-Id generated by HB2B for a payload contains spaces if the MessageId of the message does so. This results in an invalid Content-Id but also in failure when executing WS-Security signing.

Note that a MessageId containing spaces is invalid in itself and therefore not be used by back-end systems anyway.