Hi, I integrated Ranger with Nifi and configured Multi-Tenancy. But for some processes like below they don't have access to add it in their canvas. I added R/W permission to /flow and RW to their process group in Ranger. Not sure what permission i missed. Any thoughts? TailFile, PutHDFS, PutFile, InvokeScripterProcessor, GetHDFSSequenceFile, GetHDFS, GetFile, FetchHDFS, FetchFile, DeleteHDFS, ExecuteStreamCOmmand, ExecuteScript, ExecuteProcess, ExecuteFlumeSource, ExecuteFlumeSink ... View more

Hi , I integrated Ranger and Nifi and also configured multi-tenancy. I have a R/W to /proxy, R/W to /flow and R/W to all - nifi-resource. Could you please help what policy should i add in Ranger for the connection ? i would like to list queue, empty queue ,etc. I tried /flowfile-queues /View_Data but didn't work. Thanks, SJ ... View more

Hi, I ran a simple query with executeSql process (select * from piers.status) but it created 10k duplicate messages in the success queue and all the massages are the same. Just wondering if i missed anything in the configuration Thanks SJ ... View more

Hi, I followed the following post : https://community.hortonworks.com/questions/61159/getting-untrusted-proxy-message-while-trying-to-se.html I have a questions, Is the policy in the authorizations.xml file is right? if now, how it should be? authorizers.xml : <authorizers> <authorizer> <identifier>file-provider</identifier> <class>org.apache.nifi.authorization.FileAuthorizer </class> <property name="Authorizations File">/var/lib/nifi/conf/authorizations.xml</property> <property name="Users File">/var/lib/nifi/conf/users.xml</property> <property name="Initial Admin Identity">CN=TTTTT, OU=TTT</property> <property name="Legacy Authorized Users File"></property> <property name="Node Identity 1">CN=XXXXXX OU=XXXXX</property> </authorizer> </authorizers> Users.xml: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <tenants> <groups/> <users> </users> </tenants> authorizations.xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <authorizations> </authorizations> ... View more