Member since
10-19-2016
13
Posts
0
Kudos Received
0
Solutions
02-06-2023
05:53 AM
I am having a simple flow where I am fetching the creds for SFTP from DB and then uploading a file using the putSFTP but I am getting UnknownHostException error on PutSFTP processor. I see the creds are being fetched - I see them in logs and also tried connecting to the Server using FileZilla (creds are correct ..no space etc all good with that).. Also I tried hardcoding the creds in PutSFTP and still it did not work. can someone please guide me..
... View more
10-25-2016
02:15 PM
@Juthika Shenoy This error indicates and authorization issue. This is separate from authentication. I would start by looking at your nifi-user.log and see what DN is successfully authenticating by being denied authorization. Then verify that DN is included along with your node identity(s) in the users.xml file. If it is not, then that is your problem. I noticed from your post above you never provided an "Initial Admin Identity" in your authorizers.xml file. This is a must in order to get an initial admin added to the system so that that initial admin can then add additional users via the UI. You can take your user DN from the nifi-user.log and add it to your authorizers.xml file: <property name="Initial Admin Identity">Add user DN Here</property> Also make sure you still have your Node Identity(s) set in the authorizers.xml file as well.
<property name="Node Identity 1">DN From Node 1 Cert Here</property>
<property name="Node Identity 2">DN From Node 2 Cert Here</property>
etc..... If every Node is using the same cert. That cert must have a Subject Alternative Name (SAN) entry for each nodes FQDN. From a security standpoint, it is not recommended using one cert for multiple servers. Finally, you will need to stop your NiFi nodes, delete your existing users.xml and authorizations.xml files form each of them, and then restart. NiFi will only create those tow files once. Once they have been created, changes to the authorizers.xml file will not trigger updates to them. Thanks, Matt
... View more