https://community.cloudera.com/t5/Support-Questions/Nifi-1-1-site-to-site-permissions-are-disabled-within-the/m-p/224584#M186448 <P><A rel="user" href="https://community.cloudera.com/users/78176/xaviercoudre.html" nodeid="78176" target="_blank">@Xavier COUDRE </A> <BR />There are multiple policies needed for S2S to work.</P><P>The first policy is a "Global" policy (Found under "Policies" via the hamburger menu in upper right corner of NiFi UI):</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="72455-screen-shot-2018-04-25-at-12918-pm.png" style="width: 296px;"><img src="https://community.cloudera.com/t5/image/serverpage/image-id/15495i7CF24FF0A2D328A4/image-size/medium?v=v2&amp;px=400" role="button" title="72455-screen-shot-2018-04-25-at-12918-pm.png" alt="72455-screen-shot-2018-04-25-at-12918-pm.png" /></span></P><P> You must authorize the source NiFi instance(s) (This would be any NiFi instance running a RPG trying to connect to this NiFi). This allows the RPG to communicate with the target to retrieve details such as number of connected nodes, load on those nodes, list of authorized input and output ports and supported connection information (node hostnames, is RAW transfer enabled, what is RAW port...)</P><P>-</P><P>In order for any ports to be returned, the source NiFi instance(s) must be authorized in those ports. I believe this is the step you have already completed which we were discussing initially in this answer.</P><P>-</P><P>Thanks,</P><P>Matt</P><P>-</P><P>HCC Forum Tip: Try to avoid responding to an existing answer with a new answer. Comment on answer instead. It makes discussion easier to follow, especially when multiple answer are being discussed.</P> Sun, 18 Aug 2019 01:43:07 GMT MattWho 2019-08-18T01:43:07Z