By Juergenkress-Oracle on Jan 18, 2015
When working with a colleague on a sample SOA 12c project recently I noticed a change in 12c that I had not seen mentioned anywhere yet. In the sample project we were integrating with the Atlassian OnDemand service in order to provision users for Confluence and JIRA. The integration is performed using a SOAP service over SSL. In this situation, like at many of our customers, we needed to import additional trusted certificates into the trust store in order to make the service call over SSL. At many of our customers this is an internal Root CA they use to sign their own certificates for internal use.
When looking at the default settings of the IntegratedServer in JDeveloper 12c we can now see below that it is configured by default to use the OPSS Keystore Service and not a JKS Trust Store.
You can see above that instead of a filesystem URI to a JKS file you now see a kss:// URI. This URI shows that we are using the trust store called "trust" in the system strip of the Keystore Service.
The OPSS Keystore Service is meant to provide a single location for Keystores and Trust stores for all applications running within the Weblogic domain. The only pre-requisite for using the service is that the JRF templates have been applied to your domain, which should be the case for any SOA 12c domain.
Using this service you can now manage all of your
certificates through Fusion Middleware Control and WLST. You can
navigate to the Security -> Keystore menu under your domain in FMW Control as shown below. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.