You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Wenzhe Zhou (Jira)" <ji...@apache.org> on 2021/05/10 19:48:00 UTC
[jira] [Assigned] (IMPALA-10678) Support custom SASL protocol name
in Kudu client
[ https://issues.apache.org/jira/browse/IMPALA-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenzhe Zhou reassigned IMPALA-10678:
------------------------------------
Assignee: Wenzhe Zhou
> Support custom SASL protocol name in Kudu client
> ------------------------------------------------
>
> Key: IMPALA-10678
> URL: https://issues.apache.org/jira/browse/IMPALA-10678
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Attila Bukor
> Assignee: Wenzhe Zhou
> Priority: Major
>
> As of KUDU-1884, Kudu supports custom Kerberos principals on server-side and custom SASL protocol (service) names on client-side which must match the SPN base, i.e. if the SPN is kudu/_HOST, SASL protocol name must be "kudu" in the client to be able to connect to the cluster.
> On the client-side, this can be set on the client builder:
> https://github.com/apache/kudu/blob/dc5b5bd899755faa506363bd00d3bbbac8d594d3/src/kudu/client/client.h#L308-L320
> https://github.com/apache/kudu/blob/dc5b5bd899755faa506363bd00d3bbbac8d594d3/java/kudu-client/src/main/java/org/apache/kudu/client/AsyncKuduClient.java#L2895-L2909
> Users should be able to set this in Impala to be able to connect to a Kudu cluster with non-default SPNs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org