Matthew Clarke created NIFI-2988:
------------------------------------
Summary: Decouple S2S Raw protocol from NiFi's web http(s) ports
Key: NIFI-2988
URL: https://issues.apache.org/jira/browse/NIFI-2988
Project: Apache NiFi
Issue Type: New Feature
Components: Core Framework
Affects Versions: 1.0.0
Reporter: Matthew Clarke
Priority: Minor
The mutual authentication and encryption added when S2S is set to secure add
overhead that may no be necessary in every user environment. I may want to
have my NiFi web UI secured with controlled multi-tenancy access, but still
have my S2S run non-secure.
When using the RAW protocol, I should be able to define different http and
https connection end-points from the NiFi web UI endpoints and specify which
hostname/port to run those on.
This will allow me to have my Web UI secured on a public or internal network
and have my S2S configured independent of that as secure or non-secure on my
internal network. That way a user can eliminate the Security overhead when
using s2S on a closed internal network.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
