I'm not sure if this will solve your problem, but let's take a look at the command here: ./knoxcli.sh create-alias ldcSystemPassword --cluster MyCluster --value Password@123 If we refer to the Knox User Guide (https://knox.apache.org/books/knox-0-9-0/user-guide.html#Special+note+on+parameter+main.ldapRealm.contextFactory.systemPassword) subsection on using ALIAS for the password you see the wording: Assuming the plain text password is “hadoop”, and your topology file name is “hdp.xml”, you would use following command to create the right password alias in credential store. ./knoxcli.sh create-alias ldcSystemPassword --cluster hdp --value hadoop It looks as if you need to specifically name the cluster the same as the topology file name. It appears the file you've attached was 'default.xml' so instead you might want to try: ./knoxcli.sh create-alias ldcSystemPassword --cluster default --value Password@123 On the other hand you could also try renaming the file to "MyCluster" as well. ... View more

Typically the GetFile processor it pulls it into NiFi so you can do some type of processing or routing. It doesn't really put the file anywhere in particular. You should use something like the PutFile processor to move the file to a location of your choosing. Just make sure to route the success relationship to the PutFile processor and configure the PutFile processing to your liking. GetFile PutFile ... View more

If you're on azure the port may just be port 22. Port 2222 is for Sandbox users. Try without the port argument. ... View more

Looks like a typo. The forwarded ports which are a part of the Sandbox include only 8983. We'll get it updated @jmedel ... View more