Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

I deleted the authorizations.xml and user.xml files on all the nodes of the cluster and restarted the nodes. The Nifi nodes do not start up and I see the following errors int he logs now:- 2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr Failed to start web server: Error

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

We have no wild cards in the certificates created.Each node certificate has a unique CN name same as that of the hostname. -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Thanks for the suggestions. I tried exactly the same step and deleted authorizations.xml and user.xml from all the cluster nodes and tried starting the nodes.I am encountering the below error while starting the nodes now and the node does not start now. 2018-09-20 08:20:09,003 ERROR [NiFi logging

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Thanks for the reply.Please find below the authorizations.xml and user.xml;- Authorizations.xml:- - - - - - - - - - - - - - - user.xml:- - - Errors in the user logs:- 2018-09-19 05:25:14,267 INFO [NiFi Web Server-22] o.a.n.w.a.c.IllegalStateExceptionMapper java

Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Hello, We are trying to integrate Nifi-7.1 with SSL and LDAP. We have two different Nifi installation,one which is a standalone node and the other which is a three node cluster. Nifi Standalone:- We were able to successfully integrate the Standalone node with SSL and login to the Nifi UI with th

How to trust another certificate from within nifi flows?

Hello Experts, We have a Nifi cluster without certificates or SSL implementation. We have a requirement to call another url/interface from the Nifi flows using https url since the end point is configured with SSL. The "https" end point uses a self signed certificate and in order to trust the certi

Re: Nifi Site-to-Site pre-existing deployments do not work after enabling TLS and Ldap

Thanks Mark, I had a follow up question though. Let's say you have a nifi flow with site-to-site deployment between two nodes node-1- source and node-2 destination on a non secure cluster. The default http port "8080" is used in the configuration of the RPG on node which is http://node-2:8080/

Re: ERR_BAD_SSL_CLIENT_AUTH_CERT error after configuring secure cluster

Thanks Bryan and Andy for the advice. As Brian mentioned,the issue was with running the toolkit command multiple times. I ran it freshly with all the host names at once and it works fine. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/ERR-BAD-SSL-CLIE

ERR_BAD_SSL_CLIENT_AUTH_CERT error after configuring secure cluster

Hello Experts, I have secured my three node nifi cluster and followed the links below:- https://pierrevillard.com/2016/11/29/apache-nifi-1-1-0-secured-cluster-setup/ https://pierrevillard.com/tag/tls-toolkit/ The only difference is that I used the toolkit standalone mode to generate the require

Re: Nifi Site-to-Site pre-existing deployments do not work after enabling TLS and Ldap

Thanks Mark. That really helps.Appreciate it! -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Site-to-Site-pre-existing-deployments-do-not-work-after-enabling-TLS-and-Ldap-tp16486p16493.html Sent from the Apache NiFi Developer List mailing list archi

Re: Nifi Site-to-Site pre-existing deployments do not work after enabling TLS and Ldap

Basically, on the destination Nifi cluster,at a Global Policy level,I have enabled "Retrieve Site-to-Site" for the source nifi user. On the default root Nifi-flow processor,on the input port,I can see the policy "Receive site-to-Site" However,when I create a new Process Group ,let's say Test and

Nifi Site-to-Site pre-existing deployments do not work after enabling TLS and Ldap

Hello Team, We have two environments of Nifi ,one whihc is a standalone and the other whihc is a cluster. I have upgraded the Nifi (standalone as well as cluster) in our non prod environment from 1.1.1 to 1.3.0 ,Implement TLS and also integrate with LDAP. I followed the process mentioned in the

Re: Not able to start nifi nodes when clustered

Thanks Mark. I did the same and have got the embedded zookeeper running only on one of the nodes now. Both the nodes are up now. However,I am not able to connect to the UI now. It runs on the default port 8080. root@hostname-1/opt/nifi/test/nifi-1.3.0/logs# netstat -an |grep tcp0

Re: Not able to start nifi nodes when clustered

I was able to get over this.There was a typo and I can now start the two clustered Nifi nodes. However, I keep on getting the below messages on both the nodes when I try to start them. 2017-06-29 13:03:58,537 WARN [main] o.a.nifi.controller.StandardFlowService There is currently no Cluster Coordi

Not able to start nifi nodes when clustered

I am trying to set up a fresh nifi cluster with 2 nodes.Details below:- OS-104-Ubuntu Nifi version 1.3.0 jdk - Oracle jdk-1.8.0_131 I tried to start the nifi nodes in a non clustered mode and both of them started up fine. After that,I have been trying to set up the 2 node nifi cluster and it fail