Hello, Site-to-Site is a feature that is only available for the Input Ports and Output Ports on the Root Process Group. I.e., you cannot enable site-to-site on Input Ports and Output Ports within a child Process Group.
The function of an Input Port or an Output Port in NiFi is to get data into or out of a Process Group. So as data flows through your flow, it can enter a Process Group via its Input Port(s) and when it's finished the Process Group, it will exit back up to the parent Process Group's components via the Output Port. The idea behind site-to-site was to treat a NiFi instance's Root-level Process Group like other Process Groups, by allowing you to send data into them using Input Ports/Output Ports. Then you simply send to the Root-level Process Group from another instance by using a Remote Process Group. So typically if you want to push data into a child Process Group, you will create an Input Port on the Root-level Process Group, and then connect that Root-level Input Port to your child Process Group's Input Port. Does that make sense? Thanks -Mark > On Jul 24, 2017, at 8:07 AM, nifi-san <[email protected]> wrote: > > 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 then try to > create an Input Port ,I see that the option "Receive Site-to-Site" is grayed > out. > > What is a user already has site-to-site deployment on a non default process > group such as test prior to configuring authentication and authorization? > > > > > > > > > > > -- > 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-tp16486p16488.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
