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

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

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

[hms] KUDU-1884 Add support for custom SASL protocol name

This patch adds support to set a custom SASL protocol name
when using the KuduMetastorePlugin in the HMS. Because
there isn’t a good way to pass configuration the plugin
today, it uses an environment variable instead.

The patch updates the master_hms-itest to use the new
custom SASL protocol name feature to validate functionality.

Change-Id: Id8d9e208da1d767bb24470ab031a5266461d070b
Reviewed-on: http://gerrit.cloudera.org:8080/17350
Reviewed-by: Grant Henke <granthe...@apache.org>
Tested-by: Grant Henke <granthe...@apache.org>


> 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
>
> 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)

Reply via email to