[
https://issues.apache.org/jira/browse/NIFI-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186154#comment-15186154
]
ASF GitHub Bot commented on NIFI-1488:
--------------------------------------
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/253#issuecomment-194034813
I looked at the Hadoop source code a little bit, but without getting too
deep, it does appear that it could change during the lifetime of an application:
1. Hadoop/HBase is configured with Kerberos
2. NiFi is started and HBase processor is added and configured to use
Kerberos to connect (processor properties not saved yet, perhaps?)
3. HBase is no longer using Kerberos
4. NiFi HBase processor `customValidate` is run and uses "cached" value of
`isSecurityEnabled() == true`, even though Kerberos is no longer valid for this
client
That's why I think the `UserGroupInformation.isSecurityEnabled()` call
should still be executed during the `customValidate` call of the processor. To
me, that seems "closer to true" than the alternative.
> 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
>
> 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)
