[
https://issues.apache.org/jira/browse/NIFI-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250884#comment-17250884
]
Noe edited comment on NIFI-7786 at 12/17/20, 2:08 PM:
------------------------------------------------------
I have run into this issue and would like to see this option put back. As Nifi
is used in various POCs it is advantageous to allow flexibility.
"it can be imported into the local truststore explicitly" This is not the case.
I ran into this problem after importing a Splunk default cert into the
java/cacerts trustore that a Splunk server is using in development. A POC is
not a reasonable time to harden an environment with standard security concerns.
Can we please find a way to allow this functionality?
Little irony, GetSplunk works against the same server but trying to make a
dynamic query on Splunk utilizing rest with InvokeHttp jokes on cert validation.
was (Author: [email protected]):
I have run into this issue and would like to see this option put back. As Nifi
is used in various POCs it is advantageous to allow flexibility.
"it can be imported into the local truststore explicitly" This is not the case.
I ran into this problem after importing a Splunk default cert into the
java/cacerts trustore that a Splunk server is using in development. A POC is
not a reasonable time to harden an environment with standard security concerns.
Can we please find a way to allow this functionality?
> Bring back Trusted Hostname property from InvokeHTTP processor
> --------------------------------------------------------------
>
> Key: NIFI-7786
> URL: https://issues.apache.org/jira/browse/NIFI-7786
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Kun Deng
> Priority: Major
>
> Removing this option is a mistake. Just google how many people need this
> option for various reasons.
> It is an option so that by using it, people are willing to take the risks.
>
> Please bring back this option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
