aaron-kumar
commented
1 year ago Usage of BouncyCastleProvider as the preferred security provider (Security.insertProviderAt(new BouncyCastleProvider(), 1)) was First introduced as part of Oxalis release 4.1.7 with following code:
// Make sure that BouncyCastle is the preferred security provider
final Provider[] providers = Security.getProviders();
if (providers != null && providers.length > 0)
Security.removeProvider(BouncyCastleProvider.PROVIDER_NAME);
log.debug("Registering BouncyCastle as preferred Java security provider");
Security.insertProviderAt(new BouncyCastleProvider(), 1);It was later removed as part of Oxalis 4.1.8 when some Oxalis users started facing problem because of setting BouncyCastleProvider as the preferred security provider. Refer issue #118 with comment: - "Earlier oxalis-as4 put BouncyCastle as the preferred SecurityProvider, but that introduced several problems for some of our users. Generally it is not recommended to reorder the security provider list."
But if you can set BouncyCastleProvider as the preferred security provider within your integration code without any problem/interference with your other application then please go ahead and set that. I myself don't have visibility as what issue/s was faced by Oxalis users when it was first introduced as part Oxalis release 4.1.7 so can't comment further on this. But we will try to reintroduce this as part of some minor release after Oxalis 6.0.0 major release to understand the impact.
FrodeBjerkholt
javierestevez
dladlk
There is a performance issue when processing large files using AS4. We've been trying to process an incoming file 100 MB big and locally it was taking us 23 minutes on a fairly powerful laptop.
The issue was the security provider which somehow doesn't seem to be a BouncyCastle one as the fix in https://github.com/OxalisCommunity/Oxalis-AS4/issues/84 promised. It looks like the fix in https://github.com/OxalisCommunity/Oxalis-AS4/issues/104 somehow affected it.
Debugging revealed that the bottleneck was in AttachmentContentSignatureTransform at the line number 217.:
while ((numBytes = inputStream.read(buf)) != -1)To fix it, as discovered by my colleague @javierestevez, we introduced the following code:
@PostConstruct public void init() { Security.insertProviderAt(new BouncyCastleProvider(), 1); }to the configuration class in the spring boot project. By doing that the processing time went down to 11 seconds locally.
We are using:
Worth noting is there is no issue when using AS2.