You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2018/03/04 23:11:00 UTC

[jira] [Commented] (CALCITE-1480) TLS support for Avatica

    [ https://issues.apache.org/jira/browse/CALCITE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385426#comment-16385426 ] 

Kevin Risden commented on CALCITE-1480:
---------------------------------------

https://issues.apache.org/jira/browse/CALCITE-1538?focusedCommentId=15783768&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15783768

 

Looks like CALCITE-1538 got a start on this. Might need to focus on KeyStore next since TrustStore was added.

> TLS support for Avatica
> -----------------------
>
>                 Key: CALCITE-1480
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1480
>             Project: Calcite
>          Issue Type: New Feature
>          Components: avatica
>            Reporter: Josh Elser
>            Priority: Major
>
> We should expose the support for users to configure the Avatica server to operate using TLS.
> Some thoughts on what would be minimally acceptable:
> * Configure one-way or two-way TLS
> * Ability to specify ciphers/algorithms to disallow (prevent the use of weak/known-insecure parameters)
> This should all be easily attainable through the Jetty APIs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)