Thanks Rick. It helps, but only in identifying what my next steps are. I
may make a patch that enable some additional options for loading keystore
data in a networked+embedded setup as well as possibly programmatic access
to get/set all derby properties.
On Tue, Dec 11, 2018, 1:34 PM Rick Hillegas
For SSL/TLS protected connections, Derby relies on the SSL/TLS support
provided by the JVM. So this is a JVM-configuration question. Here is
the top answer which I get when I google for "application specific
keystore in multi-tenant java jvm":
https://stackoverflow.com/questions/1793979/registe
Hello Alex,
We are doing this:
System.setProperty("javax.net.ssl.keyStore", config.getKeyStorePath());
System.setProperty("javax.net.ssl.keyStorePassword",
config.getKeyStorePassword());
Kind Regards
Peter
Am 11.12.18 um 15:20 schrieb Alex O'Ree:
> The derby security guide for enabling tls conn
The derby security guide for enabling tls connection supports only loading
the keystore location/password from the global system properties. Is there
a way to provide this programmatically? I'd rather not define this setting
globally within the jvm as it's shared with tomcat and a number of other
c
