[jira] [Commented] (NIFI-6019) Remove Trusted Hostname property from InvokeHTTP processor

["Kun Deng (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189312#comment-17189312 ] 

Kun Deng commented on NIFI-6019:
--------------------------------

How is this an improvement??? 

So many use cases when this is necessary.  It cost hours and hours to get around it.  If a user wants to take the risk, it is their job to make sure it is worth taking. 

 

Here is an example:

I need to run nifi on a test endpoint which has an invalid cert from the prod instance.   Now I have to get the other team to fix the cert before I can run my flow? 

 

 

> Remove Trusted Hostname property from InvokeHTTP processor
> ----------------------------------------------------------
>
>                 Key: NIFI-6019
>                 URL: https://issues.apache.org/jira/browse/NIFI-6019
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.8.0
>            Reporter: Andy LoPresto
>            Assignee: Troy Melhase
>            Priority: Major
>              Labels: InvokeHTTP, certificate, hostname, http, security, tls
>             Fix For: 1.10.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> 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|https://lists.apache.org/list.html?users@nifi.apache.org:gte=1d:trusted%20hostname]) 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. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)