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 -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/1PieEUEHb2UJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
