My apologies. It is sometimes difficult to decide if the root cause of a challenge is related to code or related to a user level configuration issue. In this case I had included the developer group because it seemed it might relate to the PutFile after I had eliminated the possible configuration omissions.
On Tue, May 29, 2018 at 7:14 PM, Joe Witt <joe.w...@gmail.com> wrote: > jim > > please only post to one list. > > users is good for this. > > thanks > joe > > On Tue, May 29, 2018, 3:54 PM James McMahon <jsmcmah...@gmail.com> 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 >> >
