[
https://issues.apache.org/jira/browse/NIFI-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191482#comment-15191482
]
Bryan Bende commented on NIFI-1488:
-----------------------------------
Based on Randy's findings we definitely need to address the validation issue...
I can't answer Alan's question as to the authoritative definition of principal
names, but this is making me wonder why we don't reuse the exact same
properties from the AbstractHadoopProcessor:
https://github.com/apache/nifi/blob/a87230358d9a1f0d2676339fcd2354ae5732f6f2/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L90
I feel like we should pull out the KERBEROS_CONFIG_VALIDATOR,
KERBEROS_PRINCIPAL, and KERBEROS_KEYTAB into a KerberosProperties class in
nifi-processor-utils (or somewhere) so it can be the same across HDFS
processors and HBase. It looks like the KERBEROS_PRINCIPAL property there uses
the KEREBEROS_CONFIG_VALIDATOR which does not end up checking any kind of
pattern for the principal value.
Thoughts?
> Add Kerberos Support to HBase processors
> ----------------------------------------
>
> Key: NIFI-1488
> URL: https://issues.apache.org/jira/browse/NIFI-1488
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.4.0, 0.4.1
> Reporter: Bryan Bende
> Assignee: Ricky Saltzer
> Fix For: 0.6.0
>
> Attachments:
> 0001-NIFI-1488-Adjusting-unused-imports-and-adding-licens.patch
>
>
> Our current HBase integration does not support communicating with a
> Kerberized HBase install. We should support this just like we do for the HDFS
> processors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
