Re: Nifi Registry LDAP

That’s odd, but…. Glad it’s working for you? ☺ Thanks for letting me know. I’ll leave this for now, let me know if you run into further issues and I can look into them if the need arises again. Cheers, Kevin From: Scott Howell Reply-To:

Re: Nifi Registry LDAP

So interesting thing just happened. I added my TLS parts of the identity-provider.xml and I restarted the server and everything is working fine. I don’t want you digging into it too much but it is a strange issue I was receiving. > On Apr 10, 2018, at 3:21 PM, Kevin Doran

Re: Nifi Registry LDAP

Thanks; that certainly narrows it down. It could be that you’ve uncovered a bug with the LdapIdentityProvider when using START_TLS. I’ll try to recreate it and dig into it on my end. Thanks for sharing all this info. Kevin From: Scott Howell Reply-To:

Re: Nifi Registry LDAP

I was able to remove the TLS information in the identity-provider.xml and was able to use my remote LDAP to login. So I think I am narrowing down the issue. > On Apr 10, 2018, at 2:57 PM, Kevin Doran wrote: > > Thanks Scott, > > I don’t see anything wrong with your

Re: Nifi Registry LDAP

Thanks Scott, I don’t see anything wrong with your configuration. I created a free jumpcloud account, so I’ll try to recreate this issue and get back to you if I have any other insights. Kevin From: Scott Howell Reply-To: Date:

Re: Nifi Registry LDAP

I was able to switch back to my local LDAP server and was able to login successfully. The provider I am using in identity-providers.xml is as follows: ldap-identity-provider org.apache.nifi.registry.security.ldap.LdapIdentityProvider SIMPLE

Re: Nifi Registry LDAP

Thanks Kevin for sending that back, This is what I see when looking at the Headers on the login. The version of Nifi-Registry I am running is 0.1.0. What confuses me is that this was working with my local LDAP fine. It just stopped working when I switched to setting up the

Re: Nifi Registry LDAP

If everything is configured correctly, this error usually indicates that the server did not locate your login credentials when processing the login request. That usually means it will not even attempt to authenticate the credentials, so I'm not sure it is an LDAP configuration error. If you

Re: Nifi Registry LDAP

Yes I changed that from USE_DN to USE_USERNAME to do some troubleshooting. Sorry for not changing it back before I sent this stuff out. > On Apr 10, 2018, at 2:01 PM, Mike Thomsen wrote: > > Scott, > > In your last email, the way I read it you found part of the problem

Re: Nifi Registry LDAP

Scott, In your last email, the way I read it you found part of the problem was using USE_USERNAME and not USE_DN, have you done a full comparison of the other config with this one? On Tue, Apr 10, 2018 at 2:58 PM, Scott Howell wrote: > Yes I did, I had Nifi-registry

Re: Nifi Registry LDAP

Yes I did, I had Nifi-registry working with a local instances of LDAP running. It’s now not cooperating since I moved to using Jumpcloud. > On Apr 10, 2018, at 1:56 PM, Kevin Doran wrote: > > Hi Scott, > > Did you configure nifi-registry.properties with: > >

Re: Nifi Registry LDAP

Hi Scott, Did you configure nifi-registry.properties with: nifi.registry.security.identity.provider=ldap-identity-provider On 4/10/18, 14:53, "Scott Howell" wrote: Thanks for the all the help yesterday standing up LDAP for NIFI. I was able to troubleshoot and

Nifi Registry LDAP

Thanks for the all the help yesterday standing up LDAP for NIFI. I was able to troubleshoot and fix the issues myself. I am running into a unique issue with my Nifi-Registry when I try to login with my LDAP credentials like I do for the nifi cluster I get in my logs with this: 2018-04-10

Re: Nifi Custom processor code coverage

Take a look at TestInvokeJavascript.java. There are some samples there of manually calling customValidate. On Tue, Apr 10, 2018 at 10:28 AM, Mohit wrote: > Hi, > > > > I’m testing a custom processor. I’ve used a customValidate(ValidationContext > context) method

Nifi Custom processor code coverage

Hi, I'm testing a custom processor. I've used a customValidate(ValidationContext context) method to validate the properties. When I run coverage, that piece of code is not covered. I've used assertNotVaild() but it doesn't increase my code coverage. Is there any way to test that part? My

Re: [Nifi 1.5.0] DistributedMapCacheClientService fails to open port

Hi Guys, I didn't notice it was a client and it indeed needs a server. Adding a DistributedMapCacheServer solve the issue Thanks a lot François 2018-04-10 14:09 GMT+02:00 Pierre Villard : > Hi, > > Usually, you would start a DistributedMapCacheServer controller

Re: [Nifi 1.5.0] DistributedMapCacheClientService fails to open port

Hi, Usually, you would start a DistributedMapCacheServer controller service on a given port and use the client service to connect on this port. Is that what you tried? Pierre 2018-04-10 14:04 GMT+02:00 Andrew Grande : > It's a client, it connects to a cache service. You

Re: [Nifi 1.5.0] DistributedMapCacheClientService fails to open port

It's a client, it connects to a cache service. You need to start another service and point the client to it. Andrew On Tue, Apr 10, 2018, 6:29 AM françois lacombe wrote: > Hi all, > > Does anyone experience problems with DistributedMapCacheClientService > service?

[Nifi 1.5.0] DistributedMapCacheClientService fails to open port

Hi all, Does anyone experience problems with DistributedMapCacheClientService service? It currently doesn't manage to open port to listen on, according to lsof -i on my server. Then I got "connection refused" errors on runtime on several modules which rely on it. Is there any nifi.properties

RE: USB Camera support with MiNiFi 0.4.0 in Rasp3?

Thanks for your feedback Marc and Andy. Knowing that it is possible I will try to compile it today. Yesterday it took me some time to compile Bazel and Tensorflow (had to use an usb as swap device). Best regards, Iyán -Mensaje original- De: Marc P. [mailto:marc.par...@gmail.com]