Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/873
To help with testing/verifying this PR... Here are some relevant properties
`nifi.kerberos.krb5.file=/path/to/krb5.conf`
If this property is not set, it'll use a system one (ie /etc/krb5.conf)
```
nifi.kerberos.spnego.principal=HTTP/[email protected]
nifi.kerberos.spnego.keytab.location=/path/to/krb5.keytab
```
Before attempting to access NiFi you'll need to kinit. In order for your
browser to utilize SPNEGO you'll need to trust the domain. In Chrome:
```
defaults write com.google.Chrome AuthServerWhitelist nifi.example.com
defaults write com.google.Chrome AuthNegotiateDelegateWhitelist
nifi.example.com
```
Once the browser configuration is updated and you've successfully obtained
a ticket via kinit, NiFi will use it for authentication. You'll need to have
that user added to your users and policies in NiFi. If may be helpful, but not
necessary, to have another user that access the UI (maybe via certificate) to
set up these policies.
---
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.
---
