[
https://issues.apache.org/jira/browse/KUDU-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318003#comment-17318003
]
ASF subversion and git services commented on KUDU-1884:
-------------------------------------------------------
Commit e69b3c652d0c21393015aad8e5acd5ece2098573 in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e69b3c6 ]
[java] KUDU-1884 Make SASL proto name configurable
The server-side Kerberos service principal name must match the
client-side SASL protocol name. This patch makes this configurable
through the client builder API.
Change-Id: I4a881f2cf125651277927b43a5b31afc173a9bab
Reviewed-on: http://gerrit.cloudera.org:8080/17280
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Attila Bukor <[email protected]>
Reviewed-by: Grant Henke <[email protected]>
> 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)
