Unable to login to secured nifi cluster via UI

2019-08-07 Thread Mohit Jain
Hi team, I'm not able to open the nifi canvas in the secured NiFi. It shows the following error message once I provides the credentials - *No applicable policies could be found. Contact the system administrator.* [image: image.png] Kindly help. Thanks, Mohit

Re: Unable to login to secured nifi cluster via UI

2019-08-07 Thread Pierre Villard
Hi Mohit, The initial admin you configured is the user you should use for the first connection in order to grant authorizations to additional users/groups. The initial admin should have been automatically added in the authorizations.xml file created during the first start of NiFi. Hope this

Re: Communication Error Between NiFi and Registry: Error retrieving all buckets

2019-08-07 Thread Bryan Bende
I don't think there should be quotes around the NiFi identity... You have: identity="CN=nifi.example.com, L=Anytown, ST=IN, C=US" It should be: identity="CN=nifi.example.com, L=Anytown, ST=IN, C=US" On Wed, Aug 7, 2019 at 10:02 AM Nathan Maynes wrote: > > Thanks for that information Nathan.

Re: Communication Error Between NiFi and Registry: Error retrieving all buckets

2019-08-07 Thread Nathan Maynes
Thanks for that information Nathan. I went ahead and updated the Nifi-Registry user to have the name "CN=nifi.example.com, L=Anytown, ST=IN, C=US", which was copied out of the certificate that NiFi is using as its keystore, as defined in nifi.properties -> nifi.security.keystore. The error

Re: Communication Error Between NiFi and Registry: Error retrieving all buckets

2019-08-07 Thread Nathan Maynes
I tried with and without the quotes. I am getting the same error. Do I need to be restarting NiFi or using a clean browser session each time I make an update? My intuition says no since the authentication should be happening server side but wondering if I am missing something. On Wed, Aug 7, 2019

Re: Custom Processor Upgrade

2019-08-07 Thread Bryan Bende
Hello, Most likely your processor built against 1.6 would run fine in 1.9, but to make sure you just need to update any nifi dependencies in your poms to 1.9.2. If you created your project from the archetype and didn't change anything, then this should just be changing the parent in the root pom

Re: Communication Error Between NiFi and Registry: Error retrieving all buckets

2019-08-07 Thread Bryan Bende
Hard to say why it's not working, but it should be setup in the following way... In registry, there needs to be two users... 1) nmay...@example.com This user needs read access to at least one bucket, or needs read to all buckets in the special privileges. 2) CN=nifi.example.com, L=Anytown,

Custom Processor Upgrade

2019-08-07 Thread Bimal Mehta
Hi, If we have a custom processor that was created with NiFi 1.6, what are the steps we need to follow to make it work in 1.9? Is there some sort of steps that explains the jar and pom updates we need to do for making it work in 1.9?

NIFI 1.9.2 PutMongo Indexes

2019-08-07 Thread William Gosse
Is there any way to have Mongo create an index the first time it puts a document into a collection. It creates the database and collection just find if they don't exit. I like to have add indexes as well.

Re: Custom Processor Upgrade

2019-08-07 Thread Bimal Mehta
Thanks Bryan. My custom processors are part of a template. However when I try to import my template in NiFi 1.9, I get an error message saying PutFeedMetadata is not known to this NiFi instance. I did update all the dependencies to NiFi 1.9 and even the plugins. We are using a Cloudera distributed

Re: NIFI 1.9.2 PutMongo Indexes

2019-08-07 Thread Mike Thomsen
I believe you can define all of your indices in advance if you know what your data looks like. We have no plans to have NiFi get that deep into managing Mongo because it's something that could really get out of control if misused/misconfigured. Thanks, Mike On Wed, Aug 7, 2019 at 3:38 PM

Re: Custom Processor Upgrade

2019-08-07 Thread Mike Thomsen
If it's happening immediately upon trying to import the template, I believe that's the error message saying that the 1.9 instance cannot find the NAR file which provided the processor. Also, if you're referring to 1.9.0 and not 1.9.2 you're going to want to upgrade to the latter because there are