Reload certs while server is running.

Question

Sorry, i re-reply but this time i format the code.
Hi guys, hope you're doing great. Here's my question:
Is there any way to reload my truststore while the server is running?
I mean, i'm using mutual authentication in a client -server shceme. At the server side, i have a keystore and a truststore. The fact is that when i run the server, i set the properties with :
System.+setProperty+("java.net.trustStore", "My_TrustStore");
and it work fine.
Then, while the server is running, using the keytool, i create and import another cert to the trustStore (My_TrustStore), but the new client cann't connect to the server with this new cert ´cause the server cann't find it at the trustore.
At this point, if i stop the server and start it again, the new clilent can get a connection to the server using the new cert.
Is there anyway to reload the trustore while the server is running?
Hope you understand the problem and can help me. If anybody knows about a good tutorial, info, article, link, or whatever help me to understand how the SSL Api works, i'll thank you.
Here's the code of my server, this may clarify how i'm trying to do this:
public static void main(String[] args) throws Exception {
loadTrustStore();
ServerSocketFactory ssf = SSLServerSocketFactory.getDefault();
ServerSocket ss = ssf.createServerSocket(3000);
SSLServerSocket sss = (SSLServerSocket)ss;
sss.setNeedClientAuth(true);
while(true){
loadTrustStore();
MyThreat t = new MyThreat(ss.accept);
public static void loadTrustStore(){
System.setProperty("javax.net.ssl.keyStore", keyStore);
System.setProperty("javax.net.ssl.keyStoreType",keyStoreType);
System.setProperty("javax.net.ssl.keyStorePassword", kesStorePassword);
System.setProperty("javax.net.ssl.trustStore", trustStore);
System.setProperty("javax.net.ssl.trustStoreType",trustStoreType);
}this code is for testing purpouse only, but i guess you'll get the idea, i'm trying to update the truststore every time a new client is comming.

Answer 1

You shouldn't need to do any of that as long as the clients use CA-signed certificates. The truststore will trust them.
These issues usually arise when people try to use the truststore for authorization (is this person allowed to connect?) as well as authentication (is this person who he says he is?) That's not what it's for. It is only to establish an authenticated identity. Tomcat et al all have well-defined authorization schemes, in fact Tomcat has several. Use them.