SSL per connection
------------------
Key: DERBY-3822
URL: https://issues.apache.org/jira/browse/DERBY-3822
Project: Derby
Issue Type: Wish
Components: JDBC
Environment: Any
Reporter: EDAH-TALLY
This is a feature request, not a bug.
It concerns SSL client/server communication, with Derby running on a remote
server and queries through JDBC by clients.
SSL communication is already implemented in Derby and that's great. A client
app can authenticate itself and can authenticate the server. This is done by
using system properties pointing to a keystore and to a truststore. It would
give more flexibility to client JDBC apps if different keystores and
truststores can be used independantly by JDBC connection objects in the same
client app(same JVM). Each JDBC connection object would specify what keystore
and truststore to use. An example can be seen with MySQL using SVN ConnectorJ
(official ConnectorJ 5.1.6 is buggy with regards to this particular aspect).
This is just a wish.
Regards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
