Replies: 1 comment 1 reply
-
|
Yes, that is currently not supported. I created #139 to deal with that properly. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
It is now implemented and will be part of release 2.2.0. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Right now, in the
AS4RequestHandlerthe sameIAS4CryptoFactoryis used for decryption/signature verification as well as for signing/encrypting the response message (signal/error) message.In the German BDEW process, different keys must be used for encryption and signature purposes. Right now, since the same crypto factory is used, the response message will be signed with the private key defined in the crypto factory, which actually is the private key used for decryption.
Here, a different private key must be used.
Is there currently a way to achieve this, or would a change be necessary in the
AS4RequestHandlercode, like two separateIAS4CryptoFactoryinstances?Beta Was this translation helpful? Give feedback.
All reactions