You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2014/12/08 15:43:12 UTC

[jira] [Created] (NIFI-136) When site-to-site refers to self, can get authorization errors that should not occur

Matt Gilman created NIFI-136:
--------------------------------

             Summary: When site-to-site refers to self, can get authorization errors that should not occur
                 Key: NIFI-136
                 URL: https://issues.apache.org/jira/browse/NIFI-136
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core Framework
            Reporter: Matt Gilman
            Priority: Minor


In the StandardRemoteProcessGroup, we periodically refresh the peers from the remote instance. In order to do this, we choose arbitrary Input Port as the target, simply because we will get the same results regardless of the Port.

However, this makes the assumption that we have access to communicate with all Ports that we know about. When referring to your own cluster, though, we don't ask the NCM for the list of Ports; we simply use the Ports that we know about. As a result, we could choose a Port for which we have not given ourselves access. This results in a Bulletin showing up indicating that we don't have access when we refresh peers.

This is harmless but annoying and scary when the bulletin is seen.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)