[NIFI-5559] Allow usage of Trusted Hostname on all HTTP-accessing processors

• Type: Wish
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.7.1
• Component/s: Core Framework
• Labels: http https tls
• Assignee: Andy LoPresto
• Reporter: Colin Dean
• Created: 28/Aug/18 21:42
• Updated: 12/Feb/19 20:54
• Resolved: 12/Feb/19 20:54

Description

I've used several PutHTTP and GetHTTP processors in a workflow for development before realizing that I cannot configure a Trusted Hostname property for those like I can for InvokeHTTP. Configuration and setup limitations of the SSLContextService have me wanting to avoid it at all costs.

I think the workaround is to use InvokeHTTP in place of the others but it'd be nice to be able to set a trusted hostname anywhere that an SSLContentService can be used.

Issue Links

• is superceded by: NIFI-6018 Mark GetHTTP and PutHTTP as @Deprecated
• is superceded by: NIFI-6019 Remove Trusted Hostname property from InvokeHTTP processor