Hi Jim, LDAP for authentication and authorizations in NiFi has nothing to do with the processors. How processors are running/working is completely independent to the authN/authZ model you configure for NiFi.
Regarding your error, I'd say that you get this error because user/group you're setting in the processor configuration cannot be resolved at OS level (even though they exist in the LDAP, but again, that's totally unrelated). Something you can quickly check: can you resolve the username/group on the host where you're using PutFile processor? What do you get if you execute the following command: id <username>? Pierre 2018-05-30 1:14 GMT+02:00 Joe Witt <[email protected]>: > jim > > please only post to one list. > > users is good for this. > > thanks > joe > > On Tue, May 29, 2018, 3:54 PM James McMahon <[email protected]> wrote: > >> Good evening. I have recently migrated my nifi service host server from >> local resolution of users and groups to use an LDAP server. I configured >> login-identity-providers.xml and nifi.security.user.login.identity.provider. >> I verified my configuration is known to NiFi by first restarting my nifi >> service and then attempting a login to the URL by a user without a cert, >> forcing it to resolve using LDAP. This appeared to work. >> >> I then attempted to set my file owner and file group in a PutFile to a >> user and a group that are each in the LDAP. The PutFile throws a Warning >> for both owner and group: java.nio.file.attribute. >> UserPrincipalNotFoundException. The file is still output by the >> processor. It appears to default the user and owner to nifi. >> >> A cursory review of the PutFile source shows that PutFile employs >> getUserPrincipalLookupService() when it seemingly tries to validate the >> user and group. >> >> How can I get this to resolve through the LDAP for the PutFile? >> >> Thanks for any insights. -Jim >> >
