The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • December 21, 2015

SOACS plus DevCS - Chapter 16

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service.

< Previous Chapter | Next Chapter >

Chapter 16 - Securing Deployment With SSL

Out of the box, a SOACS instance encrypts SSL traffic using a self-signed certificate. 

You can retrieve this certificate using your browser (usually you click the lock next to the address bar and navigate to the "export" option) and then use keytool to import the certificate into your truststore.  Alternatively, you can use the following github project to store the certificate:


javac InstallCert.java

java InstallCert oc-129-152-358-267.compute.oraclecloud.com

This will create a truststore called "jssecacerts" with a password of "changeit" and import the certificates from the host into it.

You should do the same with the AdminServer as OSB deployment goes through AdminServer.

Once you have the certificate in a truststore, you can upload the file to your git repository and use it in the Maven command line:

mvn clean verify \

-Djavax.net.ssl.trustStore=/path/to/jssecacerts \


"changeit" is the default password.  You can/should change it using the keytool utility or extra argument to InstallCert utility.

I have heard, but have not confirmed, that the above only works with JDK8, so make sure you check your Hudson settings to ensure the correct JDK is being used.

Helpful links:

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.