Encyption key passed in the JDBC Url

[Kris]

Hi,

  I have a requirement which would require encryption keys to be maintained on the server side of our client-server application. When the user logs in via the client every time, the encryption key is available on the client in its memory received as a response value to the login call. We would like to cycle these keys on a regular basis on the server. My question is - would it be possible to pass the encryption key via the JDBC url parameters instead of pointing to the file (like   jdbc:derby:salesdb;encryptionKey=6162636465666768;newEncryptionKey=6862636465666768 in Apache Derby). I would appreciate if anyone can share ideas along these lines.

Thanks,

Kris

[Thotheolh]

There isn't such a feature for H2 unless you are refering to how H2
encrypted database decryption is done via the user password in this
format of "encryption password"<spacing>"database password".

If you are using encryption for H2 database, your JDBC would appear
something like: "jdbc:h2:~/test;cipher=AES;" and the example password
would be "password password" which the 1st "password" refers to the
database encryption password and the 2nd "password" refers to the
database own password.

[Thomas Mueller]

Hi,

I'm not sure, did you already read the H2 documentation?

Regards,

Thomas