Willem, as always, thank you for your direction! that was exactly the problem. I missread the FAQ.
I used the following and it worked perfectly: <http:destination name="{urn:ihe:iti:pdqv3:2007}pdqSupplier.http-destination"> </http:destination> <httpj:engine-factory> <httpj:engine port="${nextgate.ms.hl7v3.pdq.listenport}"> <httpj:tlsServerParameters> <sec:keyManagers keyPassword="${nextgate.ms.sec.privatekey.password}"> <sec:keyStore type="JKS" password="${nextgate.ms.sec.keystore.password}" file="${nextgate.ms.sec.keystore.file}" /> </sec:keyManagers> <sec:trustManagers> <sec:keyStore type="JKS" password="${nextgate.ms.sec.truststore.password}" file="${nextgate.ms.sec.truststore.file}" /> </sec:trustManagers> <sec:cipherSuitesFilter> <sec:include>.*_EXPORT_.*</sec:include> <sec:include>.*_EXPORT1024_.*</sec:include> <sec:include>.*_WITH_DES_.*</sec:include> <sec:include>.*_WITH_NULL_.*</sec:include> <sec:exclude>.*_DH_anon_.*</sec:exclude> </sec:cipherSuitesFilter> </httpj:tlsServerParameters> </httpj:engine> </httpj:engine-factory> Now I have a properties loading order problem. I'll post that under a different subject. thank you again! -- View this message in context: http://camel.465427.n5.nabble.com/Switching-the-CXF-Supplier-server-listener-from-HTTP-to-HTTPS-tp5722249p5722305.html Sent from the Camel - Users mailing list archive at Nabble.com.