This week's book giveaway is in the OCAJP forum. We're giving away four copies of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) and have Khalid A Mughal & Rolf W Rasmussen on-line! See this thread for details.
Would any one please be able to tell whether and SSL client can *programatically* configure its "trust store" , and *not* by using System.setProperty ?
In detail: I'm writing a client, that connects to a server using SSL. The server's certificate is *not* signed by a "well-known" CA (certificate authority). Rather, it's signed by my company's private CA.
Now, I *know* you can edit the default java trust-store file. Or you can use System.setProperty() to set the trust-store file.
But, is it possible to have finer control over the trust store ? In my case, the client has multiple threads, each thread requiring a different trust sotre - so a global "system property" is not good enough...