Hi, 1. We use SOAP with TLS for making axis based SOAP requests to an application server. It runs under osgi. The configurations for the TLS are set using System.setProperty and the functionality was working fine.
We are now developing a rest web service wrapper around it for which we use jetty and pax.web . Since the web service is required to run over https , we have configured org.osp4j.pax.web.cfg with the SSL specific configurations . Something like ... > >> org.osgi.service.http.enabled=false > > org.osgi.service.http.port.secure = 8443 > > org.osgi.service.http.secure.enabled=true > > org.ops4j.pax.web.ssl.keystore=etc/keystore > > org.ops4j.pax.web.ssl.password=password > > org.ops4j.pax.web.ssl.keypassword=password > > This fails with an illegal handshake error as client certificate is not presented. The pax web based https Rest Services work fine as long as the SOAP / TLS client bundle is not invoked, but the SOAP Web Service invocation fails when pax web is configured for https Other things that we noticed are 1. Disabling the keystore config in the pax.web.cfg , causes the issue to go away. 2. Even if the rest service is not invoked , the SOAP/TLS client fails, as long as pax web is started . Stopping bundles related to pax-web on karaf , also causes the issue to go away. So it seems that starting pax.web with https configuration is affecting the use of the system properties for TLS handshake. Can someone provide suggestions on how we can address this issue. regards Hari -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
