phase4-peppol-server-webapp cannot decrypt the incoming message due to X509PKIPathv1 #149
binaradarsha
started this conversation in
General
Replies: 1 comment 9 replies
-
Hi @binaradarsha okay, interesting. Well, that is a regression for a different profile where I thought it has no impact. I will revert the change for the Peppol profile. Please stay tuned. |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
When I send a SBDH doc using
Phase4PeppolSender.sbdhBuilder()
tophase4-peppol-server-webapp
, the incoming message header includes two BinarySecurityTokens and second one hasValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509PKIPathv1"
. Because of that decryption fails.Is this a client side problem that second BinarySecurityToken has
ValueType="...X509PKIPathv1"
instead ofX509v3
, or a lack of functionality inphase4-peppol-server-webapp
?Beta Was this translation helpful? Give feedback.
All reactions