[
https://issues.apache.org/jira/browse/KUDU-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376137#comment-17376137
]
ASF subversion and git services commented on KUDU-1884:
-------------------------------------------------------
Commit c91763c8a88d562a32763c4ae8c19644bd2f5468 in kudu's branch
refs/heads/master from zhangyifan27
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=c91763c ]
[tools] KUDU-1884 Add custom SASL protocol name for some CLI tools
This patch adds support to set a custom SASL protocol name
when using LeaderMasterProxy in kudu CLI tools.
Change-Id: If2163984fc0b144ee7ab11f2f928750925f4beeb
Reviewed-on: http://gerrit.cloudera.org:8080/17641
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <aser...@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)
