Nando Ceci

Hi, with version 3.7.0, following the howto document (i.e. using the -Dorg.openas2.cert.TrustSelfSignedCN=partner_CN parameter on the command line), I was not able to connect the outbound channel with a partner that uses a self-signed certificate. Instead, I solved it by registering the self-signed certificate in a keystore (partners_certs.jks in my case) and adding two parameters on the command line: -Djavax.net.ssl.trustStore=${binDir}/../config/partners_certs.jks -Djavax.net.ssl.trustStorePassword=keystore_password...

Hi, with version 3.7.0, following the howto document (i.e. using the -Dorg.openas2.cert.TrustSelfSignedCN=partner_url parameter on the command line), I was not able to connect the outbound channel with a partner that uses a self-signed certificate. Instead, I solved it by registering the self-signed certificate in a keystore (partners_certs.jks in my case) and adding two parameters on the command line: -Djavax.net.ssl.trustStore=${binDir}/../config/partners_certs.jks -Djavax.net.ssl.trustStorePassword=keystore_password...

Hi, with version 3.7.0, following the howto document (i.e. using the -Dorg.openas2.cert.TrustSelfSignedCN=url_del_partner parameter on the command line), I was not able to connect the outbound channel with a partner that uses a self-signed certificate. Instead, I solved it by registering the self-signed certificate in a keystore (partners_certs.jks in my case) and adding two parameters on the command line: -Djavax.net.ssl.trustStore=${binDir}/../config/partners_certs.jks -Djavax.net.ssl.trustStorePassword=keystore_password...