I have a web service to consume that uses TLS to encrypt the traffic over the wire and an X.509 Certificate to encrypt/sign the XML.
I have the target server's entire certificate chain in a JKS file called serverTrustStore.jks, and our certificate is in clientKeyStore.jks. All is well, communications work fine. Now I have to create a Mock version of said service to be hosted internally. I have coded the mock application, but my client application is having issues connecting to the mock service (which is on the same machine currently). I have enabled SSL and have verified it via the https://localhost:8443/xyz?wsdl URL. This is a Spring application running in Tomcat. In the client code I enable WS security by referencing the serverTrustSTore.jks and clientKeyStore.jks files by name. But they are also referenced in the /WEB-INF/classes/cxf/cxf-crypto.properties file, which is think is the problem. I put a run-time switch in the database to control whether mock-mode is on or off, and in the code referenced above, I change the URLs and the relevant serverTrustStore.jks file (external/internal) based on the switch. But with the "requirement"(?) that there is a file to configure the CXF bus is going to be an issue. Is this file really necessary?
