nifi/nifi-commons
Koji Kawamura ae251c1a6f NIFI-2718: Show HTTP S2S Auth error on bulletin
This commit fixes following two issues, that happens when a Root Group Port
policy for S2S data transfer is removed at a remote NiFi, after a client NiFi has
connected to that port:

1. At client side, Remote Process Group should show that authorization
is failing on its bulletin, but the Exception is caught and
ignored. Nothing is shown on the UI with HTTP transport protocol.
RAW S2S shows error on RPG bulletin. This commit fixes HTTP S2S to
behave the same.

2. At server side, corresponding input-port or output-port should show
that it is accessed by an unauthorized client on its bulletin, but it's
not shown with HTTP transport protocol.
RAW S2S shows warning messages for this. This commit fixes HTTP S2S to
behave the same.

In order to fix the 2nd issue above, request authorization at
DataTransferResource is changed from using DataTransferAuthorizable
directly, to call RootGroupPort.checkUserAuthorization().

Because the blettin is tied to the Port instance and it's
difficult to produce blettin message from this resource.

Since RootGroupPort.checkUserAuthorization uses
DataTransferAuthorizable inside, the check logic stays the same as
before.

Adding a RootGroupPortAuthorizable to provide access to necessary components for performing the authorization.

This closes #996
2016-09-08 13:43:38 -04:00
..
nifi-data-provenance-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-expression-language NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-flowfile-packager NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-hadoop-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-hl7-query-language NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-logging-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-processor-utilities NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-properties NIFI-1966: When cluster is started up, do not assume that Cluster Coordinator has the golden copy of the flow but instead wait for some period of time or until the required number of nodes have connected, and then choose which flow is correct. This closes #977 2016-09-06 16:31:37 -04:00
nifi-security-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-site-to-site-client NIFI-2718: Show HTTP S2S Auth error on bulletin 2016-09-08 13:43:38 -04:00
nifi-socket-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-web-utils NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
nifi-write-ahead-log NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00
pom.xml NIFI-2676-rc1 prepare for next development iteration 2016-08-26 11:40:58 -04:00