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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
