Hey Dave, Quite the cross-project-pollination we have going on here :)
HTTPS is not currently set up (specifically, not exposed via Avatica's HttpServer class and corresponding Builder), but this would be rather easy to do as it would just be a matter of hooking into the Jetty endpoints.
The reason I've been reticent to do it now is because the problem is much more difficult downstream. We get into key-management types of problems (which I'm sure you know vary from group to group). Perhaps putting in the functionality, suggesting _one_ way that the keystore/truststore can be managed, and then use a downstream consumer as an example of implementing that approach would be a good way to shake out issues in implementation.
I'm also not finding a JIRA issue open for the feature. I'll create one shortly -- look for the email JIRA will send on this list. If you have the cycles to put up a patch, I'd be happy to help you through the steps.
- Josh dlmar...@comcast.net wrote:
I have looked through the documentation and JIRA, and I don't see any mention of configuring the JDBC client (HTTP client) for SSL. Is this possible? If not, is it on the road map? Thanks, Dave
