You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AS4RequestHandler: how to change AS4SigningParams?
#165
We discovered an issue where our Receipt messages always used X509v3 instead of X509PKIPathv1 in the SecurityTokenReference.
Reason seems to be that in AS4RequestHandler there are multiple code paths where the AS4SigningParams are created via constructor new AS4SigningParams without the ability to modify them externally (by e.g. setting setUseSingleCertificate(false)):
Therefore, e.g. (and other places) AS4RequestHandler#_signResponseIfNeeded uses these signing params with setUseSingleCertificate(true) as default.
Is there something missing to customize the signing params?
The necessary changes were implemented in #166 and #167 and part of the 2.3.0 release.
That requires you to set the AS4CryptParams and AS4SigningParams of the AS4IncomingSecurityConfiguration object
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We discovered an issue where our Receipt messages always used
X509v3instead ofX509PKIPathv1in the SecurityTokenReference.Reason seems to be that in
AS4RequestHandlerthere are multiple code paths where theAS4SigningParamsare created via constructornew AS4SigningParamswithout the ability to modify them externally (by e.g. settingsetUseSingleCertificate(false)):Therefore, e.g. (and other places)
AS4RequestHandler#_signResponseIfNeededuses these signing params withsetUseSingleCertificate(true)as default.Is there something missing to customize the signing params?
All reactions