You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/05/25 19:26:00 UTC

[jira] [Commented] (KUDU-1884) Support customizing Kerberos principal

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

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

Commit 0569c7055cfd22be86a95fabb41e27afd570d784 in kudu's branch refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=0569c70 ]

KUDU-1884: set sasl_protocol_name for the TxnSystemClient

In clusters with a custom principal we need to set the
sasl_protocol_name on the embedded client within the TxnSystemClient.

This logic matches that in server_base.cc for server messenger
configuration.

Change-Id: Ic7b7c7fd154796215bd3a3ce748a2fd3155adebf
Reviewed-on: http://gerrit.cloudera.org:8080/17480
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <as...@cloudera.com>


> Support customizing Kerberos principal
> --------------------------------------
>
>                 Key: KUDU-1884
>                 URL: https://issues.apache.org/jira/browse/KUDU-1884
>             Project: Kudu
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 1.3.0
>            Reporter: Todd Lipcon
>            Assignee: Attila Bukor
>            Priority: Major
>              Labels: config
>             Fix For: 1.15.0
>
>
> Currently (aiming for Kudu 1.3) the Kerberos principal is hardcoded to 'kudu/_HOST'. While we have a flag to change it on the server, it isn't effective because we have no way to configure it on clients.
> The difficulty here is that there is currently no concept of Kudu client configuration files, so while we could theoretically add a new API to KuduClientBuilder, this would then mean that everyone embedding the API would have to add a new configuration, etc. We should consider a more generic key/value "connection properties" (as used by JDBC URLs) or some concept of a client configuration file (with an API to specify where to find it, etc).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)