Member since
07-30-2019
3387
Posts
1617
Kudos Received
998
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 341 | 10-20-2025 06:29 AM | |
| 481 | 10-10-2025 08:03 AM | |
| 345 | 10-08-2025 10:52 AM | |
| 374 | 10-08-2025 10:36 AM | |
| 402 | 10-03-2025 06:04 AM |
06-17-2017
02:40 AM
Hi Matt, I am configuration User Authentication with LDAP and present the following error: Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loginIdentityProvider': FactoryBean threw exception on object creation; nested exception is java.lang.Exception: The specified login identity provider 'ldap-provider' could not be found.
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:175) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1585) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1060) ~[spring-context-4.2.4.RELEASE.jar:4.2.4.RELEASE]
at org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:90) ~[na:na]
... 28 common frames omitted
Caused by: java.lang.Exception: The specified login identity provider 'ldap-provider' could not be found.
at org.apache.nifi.web.security.spring.LoginIdentityProviderFactoryBean.getObject(LoginIdentityProviderFactoryBean.java:121) ~[nifi-web-security-1.1.0.2.1.2.0-10.jar:1.1.0.2.1.2.0-10]
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
Please help me. Regards, Julio
... View more
01-24-2017
03:29 PM
1 Kudo
@Adda Fuentes Since you started your new node with a configured authorizers.xml file pointing at a legacy authorized-users.xml file, the users.xml and authorizations.xml files in NiFi 1.1 where generated from that rather then inheriting those files form your already running cluster. Clear out the setting in your new nodes authorizers.xml file, remove the users.xml and authorizations.xml files, remove the flow.xml.gz file and restart this new node. It should successfully obtain these files from your existing cluster at this point. You will need to do one additional step once this new node has joined your cluster. Since the original clusters authorizations and users will not include this new node yet, you will need to access the cluster's UI from one of the original cluster nodes using and admin account and add the new node's DN as a user and then provide that new node with all the same access policies as the your existing node have. At a minimum you need to make sure your new node is granted the "Proxy user requests" access policy: If you do not do this the following issues could occur: 1. You will not be able to access the cluster's UI via the newly added node (you will get untrusted proxy message) 2. You will still be able to access the UI via the other nodes as long as NiFi does not switch the cluster coordinator to your newly added node. You cannot restrict NiFi from picking any node in your cluster to serve this role. Matt
... View more
01-20-2017
03:05 PM
3 Kudos
@Michal R You can use an UpdateAttribute processor to change the filename. However, this would end up with every file having the same filename. Assuming each input filename is unique excpet has a .csv extension, you could do the following:
This would essentially replace the .csv extension with .avro while leaving the rest of the original filename unchanged. Thanks, Matt
... View more
01-24-2017
03:15 PM
@Balakrishnan Ramasamy
The NiFi expression language allows users to dynamically retrieve values from FlowFile Attributes, environment variables, JVM properties, or a variable registry file. Only properties that are marked as supporting expression language can be passed value dynamically. Floating your cursor over the little question mark next to any property will tell you if it support expression language or not. For sensitive property fields, the value entered is encrypted upon hitting OK. It is then stored in the encrypted format in the flow.xml.gz file. It does not support the expression language.
Please accept my answer if you feel i have addressed your question. Thank you, Matt
... View more
03-08-2018
08:49 AM
How far is the work on surfacing data provenance data in error handling? I have just discussed this option internally, rolling our own error handling process group using the data provenance rest api for looking up relevant data to convey in error logs and messages, but if on the near horizon as a built-in option, that sounds great.
... View more
01-12-2017
05:18 PM
@Matt, couple of follow up questions on Processor group with multiple input ports; 1) within the processor group, how do you distinguish between flowfiles that are coming from the various input ports. 2) in data provenance screen, is there a way to tell which flowfiles are from which input ports
... View more
01-11-2017
05:36 AM
Thank you @Matt. Will try the suggestion and revert in case I have any more follow up queries. Appreciate your help.
... View more
02-17-2017
05:44 AM
Thanks, now I can load from local
... View more
12-15-2016
02:41 PM
Thanks very much @Matt. It works!!!
... View more