Github user YolandaMDavis commented on the issue:

    https://github.com/apache/nifi/pull/915
  
    I setup 2 standalone nifi instances on separate hosts and created a 3rd 
host to serve as proxy server using Apache Web.  NiFi server A was set as the 
push server which generated 10MB Flow Files every 10 seconds. Server A referred 
to server B via a RPG. Server B received input flowfiles and saved them to disk 
via PutFile.  The following test configurations were performed:
    
    1) Unsecured NiFi instances with no Proxy  - Data was exchanged and saved 
on Server B as expected
    2) Unsecured NiFi instance with Proxy (Basic/Digest Auth) - when attempting 
to post via Proxy on Server B endpoint nifi-api/data-transfer/input-ports, 
proxy logged connection attempt with Status 407 415 (authentication required, 
post method).  Proxy logged subsequent responses of 201 or 202 for these 
attempts.  For deletes, 407/415  were logged and subsequent 200 was received 
(OK). No exception seen in log on either server. Data exchange completed 
successfully
    4) Secured NiFi Instances with no Proxy - After required policy updates in 
NiFi data was exchanged and performed as expected
    5)  Secured NiFi Instances with Proxy (Basic/Digest Auth) - Results same as 
test #2 however proxy logs did not detail resource endpoints accessed (I 
believe due to SSL enabled)
    6) Secured NiFi  instances with Proxy (No User/Pass Provided) - NiFi logged 
error indicating :  Unable to refresh Remote Group's peers due to response code 
407:Proxy Authentication Required with explanation: null.  Error Message was 
expected and resolved once user/pass provided for proxy.
    
    Given the above tests I believe that proxy authentication is working as 
expected with this patch
    
    +1
    
    Will merge into master shortly
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to