Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-2664 Moving System.setProperty for krb5.conf to NiFi startup, an… #946

Closed
wants to merge 1 commit into from

Conversation

bbende
Copy link
Contributor

@bbende bbende commented Aug 25, 2016

…d removing conflicting property from KerberosProvider config

Rather than add code to all of the Kafka processors to set the system property, it makes more sense for NiFi to set it once during start up. Then it will be available to HDFS, HBase, and Kafka processors, as well as the Kerberos login provider.

We also had a potentially conflicting property in the login provider, where you could set the krb5.conf file there which would eventually set the system property and potentially overwrite the one that could have been set from nifi.properties. Now there is on the value in nifi.properties.

…d removing conflicting property from KerberosProvider config
@YolandaMDavis
Copy link
Contributor

@bbende I can take a look

@YolandaMDavis
Copy link
Contributor

YolandaMDavis commented Aug 25, 2016

Tested this on standalone NiFi instance with 3 node Kerberized hadoop cluster. Attempted the following:

  1. Kerberos based user authentication with user set as initial admin. Was able to log in as kerberos principal and access NiFi as admin as expected.

  2. Executing a PutHDFS for generated flow files against kerberized cluster.- Was able to save to appropriate designated user folder with appropriate permissions.

+1

Will merge shortly

@asfgit asfgit closed this in 957c120 Aug 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants