[
https://issues.apache.org/jira/browse/KUDU-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailesh Mukil resolved KUDU-1965.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Commit in:
https://github.com/apache/kudu/commit/642e01190ca19882b5052739bae5508b0b38b32e
> Allow user provided TLS certificates to work with KRPC
> ------------------------------------------------------
>
> Key: KUDU-1965
> URL: https://issues.apache.org/jira/browse/KUDU-1965
> Project: Kudu
> Issue Type: Bug
> Components: rpc, security
> Affects Versions: 1.3.0
> Reporter: Sailesh Mukil
> Assignee: Sailesh Mukil
> Labels: rpc, security
> Fix For: 1.4.0
>
>
> Kudu generates certificates when TLS is enabled and if the user does not
> provide them. These certificates have Kudu specific encodings which are
> checked for in the RPC negotiation phase.
> If the certificates are user provided, it's highly likely that they will not
> contain these encodings, thus causing the certificate negotiation phase to
> fail.
> We can check for and verify these encodings if the certificates are provided
> by Kudu, else we can skip that step in the negotiation phase if the
> certificates are user provided.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
