-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AS4RequestHandler does not use correct BDEW profile crypto and signing params #166
Comments
That seems to be very related to #165 isn't it? |
Yes, this seems to be a more general issue. #165 refers to a specific signing setting. |
I am trying to get a hold of this - I totally see the issue here |
By the way |
-> #167 |
The resolution is implemented in a02ebf6 |
This should be resolved with the 2.3.0 release |
AS4RequestHandler
for handling incoming AS 4 messages seems to construct new instances ofAS4SigningParams
andAS4CryptParams
. The required parameters according to the official BDEW profile are only set inPhase4BDEWSender.AbstractBDEWUserMessageBuilder
Is this a bug or is there a way to specify the required crypto and signing params for the
AS4RequestHandler
used for incoming AS 4 messages?The text was updated successfully, but these errors were encountered: