Member since
05-23-2023
3
Posts
0
Kudos Received
0
Solutions
09-04-2023
07:45 AM
Hi everyone, I experienced the same error. After inspecting also the logs of nifi-registry, I found the error 2023-09-04 16:18:10,346 ERROR [NiFi Registry Web Server-17] o.a.n.r.web.mapper.ThrowableMapper An unexpected error has occurred: org.apache.nifi.registry.flow.FlowPersistenceException: Git directory /data/nifi01/nifi-registry-1.18.0/../nifiregistry_git is not clean or has uncommitted changes, resolve those changes first to save flow contents.. Returning Internal Server Error response.
org.apache.nifi.registry.flow.FlowPersistenceException: Git directory /data/nifi01/nifi-registry-1.18.0/../nifiregistry_git is not clean or has uncommitted changes, resolve those changes first to save flow contents. I changed to the path noted in the error message, changed to the user, which executes nifi-registry and checked the git repository status: git status Several files were modified and the git directory clearly was not "clean". I just committed and pushed everything (I had to set the git user name to make a successful commit). I don't know, why this all happend. But for now, its fixed.
... View more
05-30-2023
11:19 AM
@svenhans I would recommend you file an Apache NiFi Jira ticket for your new component processor request. https://issues.apache.org/jira/projects/NIFI Let's say an AD/LDAP lookup processor was create. that means supplying the ldap search configuration properties along with manager DN and manager password in order to do the lookup. To avoid exposing that to other users in NiFi, maybe creating an LDAPLookup Controller service would be better. Then create a processor like getLDAPUser that gets configured to use that LDAPLookup CS along with a StandardSSL CS with user defined AD/LDAP attributes to return and require a user Identity property value. Of course you run the risk of other who have access to your NiFi copying your processor and using it to fetch any details they want about your AD/LDAP users. Matt
... View more