[jira] [Commented] (KUDU-3392) Support custom certificate when Kudu acts as a client

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on KUDU-3392:
-------------------------------------------------------

Commit 152211658ef9d33e0ad727ccba46f8af24cd45b0 in kudu's branch refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=152211658 ]

KUDU-3392 Support trusting custom certificates

Right now, Kudu can only talk to Ranger KMS over TLS when its
certificate is trusted on the OS level (installed in /etc/pki). By
adding a new flag to trust a PEM file in a custom location, users don't
need to install Ranger KMS's certificate in a central location, they can
simply provide the PEM file when starting up Kudu servers. Right now,
Ranger KMS is the only such service (Kudu talks to Ranger Admin using
its Java client within a subprocess, which uses an XML config file to
set the truststore location), but it's possible that in the future, Kudu
will act as a client to other services, so the new flag,
-trusted_certificate_file, sets the trust in a central location, in
curl_util using CURLOPT_CAINFO.

A webserver-test has been updated to use the new trusted certificate
flag instead of disabling verifying the peer. The test certificate used
in this test had to be updated as well, as the original one had
CN=MyName, so the verification failed. It was valid only until 2027 as
well. The new certificate expires in 100 years and CN=127.0.0.1.

Issuer: C=US, L=Default City, O=Apache Software Foundation, CN=127.0.0.1/emailAddress=dev@kudu.apache.org
Validity
    Not Before: Aug 23 08:47:48 2022 GMT
    Not After : Jul 30 08:47:48 2122 GMT
Subject: C=US, L=Default City, O=Apache Software Foundation, CN=127.0.0.1/emailAddress=dev@kudu.apache.org

Change-Id: Ib5a69ba54ad9c0029b83417bdb4dca65b6313005
Reviewed-on: http://gerrit.cloudera.org:8080/18870
Tested-by: Kudu Jenkins
Reviewed-by: Zoltan Chovan <zc...@cloudera.com>
Reviewed-by: Alexey Serbin <al...@apache.org>


> Support custom certificate when Kudu acts as a client
> -----------------------------------------------------
>
>                 Key: KUDU-3392
>                 URL: https://issues.apache.org/jira/browse/KUDU-3392
>             Project: Kudu
>          Issue Type: Improvement
>            Reporter: Attila Bukor
>            Assignee: Attila Bukor
>            Priority: Major
>
> Kudu connects to Ranger KMS when encryption is enabled using libcurl, and if the certificate is not trusted on the OS-level, it fails to connect. It should be possible to trust a certificate file by providing it in the CLI.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)