[NIFI-6019] Remove Trusted Hostname property from InvokeHTTP processor

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.0
• Fix Version/s: 1.10.0
• Component/s: Extensions
• Labels: InvokeHTTP certificate hostname http security tls
• Assignee: Troy Melhase
• Reporter: Andy LoPresto
• Created: 12/Feb/19 20:53
• Updated: 23/Mar/22 18:09
• Resolved: 04/May/19 03:49

Description

The Trusted Hostname property in the InvokeHTTP processor is a legacy property created for a specific use in constrained environments. It now causes more problems than it solves (mailing list questions) and should not be provided as it is a security risk. Removing this property and encouraging users to correctly deploy TLS certificates when necessary is the correct path forward.

Issue Links

• is related to: NIFI-6238 Escape HTTP header names in InvokeHTTP processor
• is related to: NIFI-7786 Bring back Trusted Hostname property from InvokeHTTP processor
• relates to: NIFI-7064 Add Custom TLS Hostname Validation to InvokeHTTP
• supercedes: NIFI-3435 Allow Expression Language for "Trusted Hostname" attribute in the InvokeHTTP processor
• supercedes: NIFI-5559 Allow usage of Trusted Hostname on all HTTP-accessing processors
• links to: GitHub Pull Request #3436
• links to: GitHub Pull Request #3452