[NIFI-1857] Support HTTP(S) as a transport mechanism for Site-to-Site

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Core Framework
• Assignee: Koji Kawamura
• Reporter: Koji Kawamura
• Created: 06/May/16 06:26
• Updated: 07/Oct/16 14:07
• Resolved: 09/Jun/16 19:47

Description

We should add support for using HTTP(S) for site-to-site to be an alternative to the current socket based approach.

This would support the same push based or pull based approach site-to-site offers now but it would use HTTP(S) for all interactions to include learning about ports, learning about NCM topology, and actually exchanging data. This mechanism should also support interaction via an HTTP proxy.

This would also require some UI work to allow the user to specify which protocol for site-to-site to use such as 'raw' vs 'http'. We also need to document any limitations with regard to SSL support for this mode and we'd need to provide 'how-to' when using proxies like http_proxy or something else.

Issue Links

• is related to: NIFI-1820 Establish Site to Site as an extension point
• relates to: NIFI-1990 Implement consistent security controls for cluster, site-to-site, and API communications
• links to: GitHub Pull Request #423
• links to: GitHub Pull Request #497
• mentioned in: Page Loading...
• Wiki Page: Wiki Page Loading...