[IMPALA-10678] Support custom SASL protocol name in Kudu client

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 4.0.0
• Epic Color: ghx-label-7
• Assignee: Wenzhe Zhou
• Reporter: Attila Bukor
• Created: 26/Apr/21 18:27
• Updated: 22/May/21 00:25
• Resolved: 22/May/21 00:25

Description

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.