You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jeremy Dyer (JIRA)" <ji...@apache.org> on 2018/01/17 00:18:00 UTC

[jira] [Commented] (NIFI-4761) Allow whitelisting expected Host values

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

Jeremy Dyer commented on NIFI-4761:
-----------------------------------

So knowing this does that mean that the .host property MUST be set in nifi.properties? I just tried running a fresh NiFi 1.5.0 instance in AWS and I could not access the UI without manually specifying the public dns name in the .host property. Maybe that is a required configuration now but I was unaware of that and just wanted to know what the official stance is on that now?

> Allow whitelisting expected Host values
> ---------------------------------------
>
>                 Key: NIFI-4761
>                 URL: https://issues.apache.org/jira/browse/NIFI-4761
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Matt Gilman
>            Assignee: Andy LoPresto
>            Priority: Major
>
> NiFi has been updated to only accept requests where the Host header contains an expected value. Currently, the expected values are driven by the .host properties in nifi.properties. When running behind a proxy, the value may be the proxy host if the headers simply pass through. In this scenario, we should offer the ability to whitelist values in case updating the proxy configuration isn't possible.
> Also, the proxy documentation in the admin guide should be updated to include details regarding the Host name whitelisting. Also, should verify the context path whitelisting is documented there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)