Closed thaapaniemi closed 2 years ago
Hi @thaapaniemi which version did you use? I have a similar problem (https://github.com/OxalisCommunity/oxalis/discussions/566)
Hi @thaapaniemi which version did you use? I have a similar problem (OxalisCommunity/oxalis#566)
Hi, It probably had Oxalis 5.0.5 and Axalis-AS4 5.0.3 or something similar. If I remember correctly, downgrading the oxalis to match oxalis-as4 version fixed the proble.
Thanks @thaapaniemi , I solved the issues (https://github.com/OxalisCommunity/oxalis/issues/567)
Ciao
@thaapaniemi and @francescodiperna from you conversation, I can concluded that issue is resolved for both of you. This issue happen when there are different version of bouncycastle library available in classpath. Let me know if you have still face challenges with any release.
Note: Issue will be automatically closed if we do not hear anything from you soon.
Hi @arun, the issue is solved for me.
Di Perna Francesco
Il giorno ven 11 feb 2022 alle ore 14:38 Arun Kumar < @.***> ha scritto:
@thaapaniemi https://github.com/thaapaniemi and @francescodiperna https://github.com/francescodiperna from you conversation, I can concluded that issue is resolved for both of you. This issue happen when there are different version of bouncycastle library available in classpath. Let me know if you have still face challenges with any release.
Note: Issue will be automatically closed if we do not hear anything from you soon.
— Reply to this email directly, view it on GitHub https://github.com/OxalisCommunity/Oxalis-AS4/issues/171#issuecomment-1036222858, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV5ERW7T5VAH3BOVXTYVL2LU2UGPDANCNFSM5FYERPWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
Hi,
I have a problem for getting AS4 extensions working with Oxalis-standalone. When using AS4 extensions, certificate check will fail:
For easier reproduction I have used the version that were built from Docker image found from master branch (https://raw.githubusercontent.com/OxalisCommunity/Oxalis-AS4/master/Dockerfile) injected with certificate and test xml:
and executed this image with following docker run:
This same behaviour is found from binaries found in maven repositories and executed with local java version (openjdk version "1.8.0_292"). This was tested and built from commit 81130894b77c9b286db84535aa4c131b96baf2ad (HEAD, tag: v5.0.3)
Oxalis-standalone without AS4 extensions does work with AP:s with legacy AS2 support as expected.
Is this problem with our certificate / keystore (certificate Creation date: Oct 21, 2020; Keystore type and provider jks/SUN) or is there something else that we can do to resolve this?
Update 2021-10-18: This seems to be related with the latest release, I got it working with earlier version just fine. Used keystore type did not matter and certificate type (PRODUCTION / TEST) did not matter.