Do you mean you change the port in bootstrap.conf file?... to run nifi webui on 9090 instead of 8080 you should change in nifi.properties. change nifi web ui port to 9090/ ... View more

alternatively you can try entering username like so "hortonworks.com\karthik" ... View more

did you add like so to nifi bootstrap jvm.args.x(+1 the last arg)=-Dhttp.auth.ntlm.domain=hortonworks.com (replace with your domain)/ ... View more

try adding this to the wifi bootstrap.. http.auth.ntlm.domain = your domain .. or you can add username@domain as the user. ... View more

i am not sure wha the answer to that is. But , since nifi tracks provenance and lineage, it keeps a copy of the unencrypted file as it is the content of the original flow file , then when encrypted a new filefile is created with the encrypted content. When you decrypt, it reverts back to the original flow file and content. Basically encryption is something we did on a original file and needs to be tracked. May be some one from NiFi team can give a better answer ... View more

so you would have to create a class that extends TrustedChannelResolver and overrides the isTrusted() method. then set it in hdfs properties dfs.trustedchannel.resolver.class. I have not handled this before, but if you are up to it i can assist. ... View more

saw this in the pdfs-default xml dfs.encrypt.data.transfer false Whether or not actual block data that is read/written from/to HDFS should be encrypted on the wire. This only needs to be set on the NN and DNs, clients will deduce this automatically. It is possible to override this setting per connection by specifying custom logic via dfs.trustedchannel.resolver.class. i guess it is doable. ... View more