Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-10678

Support custom SASL protocol name in Kudu client

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Impala 4.0.0
    • Component/s: None
    • Labels:
      None
    • Epic Color:
      ghx-label-7

      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.

        Attachments

          Activity

            People

            • Assignee:
              wzhou Wenzhe Zhou
              Reporter:
              abukor Attila Bukor

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment