[
https://issues.apache.org/jira/browse/NIFI-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369091#comment-17369091
]
ASF subversion and git services commented on NIFI-8463:
-------------------------------------------------------
Commit 27c35c8c428e31a45e98e80f75e2acd735fa1276 in nifi's branch
refs/heads/main from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=27c35c8 ]
NIFI-8463: Support custom SASL protocol name in PutKudu (#5023)
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.
This patch adds the ability to configure this in the PutKudu processor.
Signed-off-by: Attila Bukor <[email protected]>
> Custom SASL protocol name support in PutKudu processor
> ------------------------------------------------------
>
> Key: NIFI-8463
> URL: https://issues.apache.org/jira/browse/NIFI-8463
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.14.0
> Reporter: Attila Bukor
> Assignee: Attila Bukor
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> KUDU-1884 allows configuring the service principal name for the Kudu
> services. The SASL protocol/service name must match the SPN base in the
> client to be able to connect to the cluster. This needs to be configurable in
> the PutKudu processor as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
