Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-19 Thread Kevin Doran
Hi Tom, If you ping nifi-registry from nifi using "localhost", then localhost is the the hostname you should use when adding the Registry client to NiFi. Let me know if this does not work for you. Kevin On February 19, 2019 at 03:33:51, Tomislav Novosel (to.novo...@gmail.com) wrote: > Hi

Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-19 Thread Tomislav Novosel
Any ideas? Tom On Tue, 19 Feb 2019 at 11:08, Mike Thomsen wrote: > Copy pasta. > > On Tue, Feb 19, 2019 at 12:51 AM Tomislav Novosel > wrote: > >> Hi Mike, Kevin >> >> Thank you for your answers, I appreciate it. >> >> @Mike, why are you setting WEB_HTTP_HOST and WEB_HTTP_PORT when you are >>

Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-19 Thread Mike Thomsen
Copy pasta. On Tue, Feb 19, 2019 at 12:51 AM Tomislav Novosel wrote: > Hi Mike, Kevin > > Thank you for your answers, I appreciate it. > > @Mike, why are you setting WEB_HTTP_HOST and WEB_HTTP_PORT when you are > using secured nifi? Shouldnt that be empty and only HTTPS host and port > used? >

Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-19 Thread Tomislav Novosel
Hi again, @Kevin, I chacked all you mentioned, containers are on the same docker network and I can ping from the Nifi container host where is Nifi registry, although they are on the same server, it is then localhost I believe. When adding nifi registry client I'm using hostname from the

Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-18 Thread Tomislav Novosel
Hi Mike, Kevin Thank you for your answers, I appreciate it. @Mike, why are you setting WEB_HTTP_HOST and WEB_HTTP_PORT when you are using secured nifi? Shouldnt that be empty and only HTTPS host and port used? BR, Tom On Mon, 18 Feb 2019, 23:56 Mike Thomsen Tom, > > > Note: both Registry and

Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-18 Thread Mike Thomsen
Tom, > Note: both Registry and Nifi are in Docker containers on the same node. I tried with IP address, but nothing. Each docker container has its own IP address. You need to link the two containers. I always use Docker Compose, so I can't help you on how to set it up manually. That said, I did

Re: How to integrate Secured Ragistry with Secured Nifi

2019-02-18 Thread Kevin Doran
Hi Tom, Given that you are getting a Connection refused exception and not an HTTP 401 or 403, I suspect that the problem is networking related and not authentication/authorization. Are the two docker containers on the same docker network? Can you resolve/ping the Registry container from the

How to integrate Secured Ragistry with Secured Nifi

2019-02-18 Thread Tomislav Novosel
Hi all, I generated standalone certificate with nifi-toolkit for my two Nifi instances and for Nifi registry instance. All are on the same domain so I used one certificate and its credentials for properties file (trustore path, keystore path, keystore passw, trustore passw). Auth is configured