You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Attila Bukor (Jira)" <ji...@apache.org> on 2021/05/25 09:15:00 UTC
[jira] [Resolved] (KUDU-1884) Support customizing Kerberos
principal
[ https://issues.apache.org/jira/browse/KUDU-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Bukor resolved KUDU-1884.
--------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
> 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)