tree 96371d752b98d9d12dbfdb21cf5a107f8e1c0686
parent 5ebbe0028b9ff4d23f86d87e4942665db62e9bc0
author Attila Bukor <abukor@apache.org> 1624570924 +0200
committer GitHub <noreply@github.com> 1624570924 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg1PwsCRBK7hj4Ov3rIwAAxBUIAJZBz43LYS9oJOJCf8kNmjQS
 01krhjVjNjUlDhe1NIwUICsgcuF7J0kBAzleTdetXXDhGc7CAOWW2mNdb/MU35Cm
 lNwFlq5V0s8/2iC4KW3HFtqOQKtEedip+eNAVEM7yv9+4Rkon6moDV0pAiSTte2G
 196jw3fYXYWYP++BCVPkelqAUfDW/CoHGKCP75m2fym9dU0+u0LWTfsK37K54Oli
 WIMlmpGJdHkiadRrAWktmHMsukYGwSPL6XR+Anpxc/lj6yikpgZM+5tSuT9dNdgn
 J/Leza1oukZdcGNOknYBeWHppC0m2RdBN4MEyNOgRzvRRUaM+ncnWQv6FOz73kM=
 =N2Kt
 -----END PGP SIGNATURE-----
 

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 <abukor@apache.org>