WSSecurityException Error #104
Replies: 4 comments 1 reply
-
Hello, The error message If you are using this in the context of Peppol, did you eventually forget to update the Endpoint certificate in the Peppol SMP??? hth, Philip |
Beta Was this translation helpful? Give feedback.
-
Thanks for the answer.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply. |
Beta Was this translation helpful? Give feedback.
-
Hello
After sending a transmission using Phase 4, I received a signal message from one of the recipients.
However, a WSSecurityException error occurred when receiving the signal message.
When I checked the signal message, I found that there were multiple "BinarySecurityToken" elements, but only one "SignatureInfo" element.
Is this something wrong with the signal message?
Or is there something wrong with the sender's configuration?
In case you are wondering, the following log is output.
Failed to process SOAP header element {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security with processor com.helger.phase4.servlet.soap.SOAPHeaderElementProcessorWSS4J@3b0c3951; error details: [ [ SingleError@0x060f77af: ErrorLevel=ERROR; ErrorID=EBMS:0102; ErrorLocation=[]; ErrorText=[Text=[Processing] The encrypted data reference the Security header intended for the \"ebms\" SOAP actor could not be decrypted by the Security Module.] ] ]
Best regards
Beta Was this translation helpful? Give feedback.
All reactions