Re: Multi Domains Nifi connection and UI acces

[Koji Kawamura]

Hello,

NiFi 1.6.0 has been released and it adds new nifi.property to
whitelist multiple hosts so that NiFi can be accessed by different
hostnames.
Please see NIFI-4761 for details. I recommend updating to 1.6.0.
https://issues.apache.org/jira/browse/NIFI-4761

Thanks,
Koji

On Wed, Apr 11, 2018 at 4:07 PM, Abdou B  wrote:
>
> Hello,
>
>  I use Nifi 1.5 and I would like to use the functionnality that enables Nifi
> to use various network interface.
> So as stated in the offficial documentation, i created the following
> properties
>
> nifi.web.https.network.interface.default=0.0.0.0
>
> nifi.web.https.network.interface.eth0=eth0
> nifi.web.https.network.interface.eth1=eth1
> nifi.web.https.network.interface.eth2=eth2
> nifi.web.https.network.interface.eth3=eth3
> nifi.web.https.network.interface.eth4=eth4
>
> I use a certificate with SAN, the SAN includes : FQDN eth0 +  FQDN eth1 +
> FQDN eth2  + FQDN eth3 +  FQDN eth4
>
> I have to use eth1 to connect to the UI
> so i set up  :
> nifi.web.https.host=the FQDN of eth0
> but I have an error stating that
> "Cluster is still in the process of voting on the appropriate Data Flow. "
>
> if I use the  eth0, I can't connect anymore (I got a message about header
> not allowed) but the cluster seems to work.
> I saw that jetty seems to be more restrictive than before and allow only
> host that use the  nifi.web.https.host to connect to UI
>
>
> would you have any advice ?
>
> Best Regards
>

Multi Domains Nifi connection and UI acces

[Abdou B]

Hello,

 I use Nifi 1.5 and I would like to use the functionnality that enables
Nifi to use various network interface.
So as stated in the offficial documentation, i created the following
properties

nifi.web.https.network.interface.default=0.0.0.0

nifi.web.https.network.interface.eth0=eth0
nifi.web.https.network.interface.eth1=eth1
nifi.web.https.network.interface.eth2=eth2
nifi.web.https.network.interface.eth3=eth3
nifi.web.https.network.interface.eth4=eth4

I use a certificate with SAN, the SAN includes : FQDN eth0 +  FQDN eth1 + FQDN
eth2  + FQDN eth3 +  FQDN eth4

I have to use eth1 to connect to the UI
so i set up  :
nifi.web.https.host=the FQDN of eth0
but I have an error stating that
"Cluster is still in the process of voting on the appropriate Data Flow. "

if I use the  eth0, I can't connect anymore (I got a message about header
not allowed) but the cluster seems to work.
I saw that jetty seems to be more restrictive than before and allow only
host that use the  nifi.web.https.host to connect to UI


would you have any advice ?

Best Regards