[
https://issues.apache.org/jira/browse/KUDU-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088149#comment-18088149
]
ASF subversion and git services commented on KUDU-3781:
-------------------------------------------------------
Commit 0b45a5f213f86976667a3b67ca38691e46a0ae68 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0b45a5f21 ]
KUDU-3781 one more test scenario for HMS Thrift TLS support
This changelist adds one more test scenario to be explicit on the
Kudu HMS Thrift client's behavior when TLS support is enabled only
at the server side. The client attempts to talk to the HMS server
without enabling TLS on its side, but turning on other types of
protection mechanisms provided by SASL such as authentication,
integrity, privacy.
This patch does not contain any functional modifications.
Change-Id: I47ab8e25507d115250fd18fcc0ff128526d4d99c
Reviewed-on: http://gerrit.cloudera.org:8080/24436
Reviewed-by: Abhishek Chennaka <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
> Add TLS transport option for Thrift client used to communicate with HMS
> catalog
> -------------------------------------------------------------------------------
>
> Key: KUDU-3781
> URL: https://issues.apache.org/jira/browse/KUDU-3781
> Project: Kudu
> Issue Type: Improvement
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.19.0
>
>
> As of time of writing, the Thrift client that Kudu masters use to communicate
> with HMS catalog doesn't support TLS transport.
> The HMS catalog allows for configuring TLS protection for connections to HMS
> clients speaking the Apache Thrift protocol. From the Kudu side, it's
> necessary to add TLS transport support to the HMS catalog client used by Kudu
> masters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
