Chakri, I can provide some background about using NiFi behind a proxy. There are a couple of key items to know when doing this.
1) NiFi is comprised of a number of web applications (web ui, web api, documentation, custom ui's, etc). So you'll need to set up your mapping to the root path. That way all context paths are pass through accordingly. For instance, if you only mapped the /nifi context path, the custom ui for Update Attributes will not work since it's available at /update-attribute-ui-<version>. 2) NiFi's rest api will generate uri's for each component on the graph. Since your coming through a proxy, you'll need to override certain elements of the uri's being generated. You can override the elements of the uri by adding the following HTTP headers when your proxy generates the HTTP request to the NiFi instance: X-ProxyScheme - the scheme to use to connect to your proxy (https in this case) X-ProxyHost - the host of your proxy X-ProxyPort - the port your proxy is listening on X-ProxyContextPath - the path you've configured to map to the NiFi instance Matt On Tue, Oct 6, 2015 at 10:32 PM, Chakrader Dewaragatla < chakrader.dewaraga...@lifelock.com> wrote: > Hi – How do I setup a nifi workflow with proxy ? Looks like ftp/http > processors has proxy property to set, we looking for a s3 processors with > proxy option. > > I am interested in two setup options: > > - Setup entier nifi cluster to use proxy server > Or > - s3 put/get/list object with proxy . > > Thanks, > -Chakri > ------------------------------ > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby notified > that any review, dissemination, distribution or duplication of this > communication is strictly prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. > ------------------------------ >
