About ckumar

ckumar · ‎03-27-2023

At a minimum, this is required in NiFi to connect to the Hdfs service secured by Kerberos. 1. Copy of core-site.xml and hdfs-site.xml file from hdfs cluster needs to be placed on nifi host to be able to configure in for Hadoop Configuration Resources property 2. Kerberos user principal and copy of keytab file on each nifi node to able to use by KeytabCredentialsService or directly configured in processor. 3. From NiFi hosts, the user who is running the nifi application "by default is nifi " should be able to obtain Kerberos tickets by using the user principal and keytab file configured in processor at step2 , from KDC server which is used by HDFS Service, so krb5.conf Kerberos client file needs to be updated to respective kdc realm details. If you found this response assisted with your issue, please take a moment and click on "Accept as Solution" below this post. Thank you

ckumar · ‎03-10-2023

Found it , So you are using this https://github.com/frank-dkvan/nifi-file-identity-provider-bundle which is a custom identity provider, and that is the reason it is not working if you upgrade the cluster. I would advise rework on you requirement related to how you would like to get Authenticated and Authorized in NiFi and I would suggest using the default ones which come from NiFi. Thank you

ckumar · ‎03-10-2023

By default, there is no such provider name "file-identity-provider" with calsscom.batchiq.nifi.authentication.file.FileIdentityProvider. nifi.security.user.login.identity.provider was always ldap or kerberos but from Apache nifi 1.14 , SingleUserLoginIdentityProvider is added as by default login.identity.provider. Running NiFi with standard HTTP is basically an anonymous remote code execution platform. Single User mode is added f puts a lock on the door, which offers basic protection. This is applicable to both Apache NiFI and Cloudera CFM NiFi Versions.

ckumar · ‎03-09-2023

Is NiFi is secure? The latest error to do with how you want to setup Authentication in NiFi and I guess the current setting is not known to nifi , Please check what is set for property value in nifi properties file nifi.security.user.login.identity.provider It should be , ldap-provider or kerberos-provider Pleaser refer https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#user_authentication Thank you

ckumar · ‎02-28-2023

Thank you for the updated information. So if you are not listing from each and every sub dir under root dir then you can use a regex pattern that just satisfies directory of your interest, Property Direceoty supports expression language. Thank you

ckumar · ‎02-28-2023

It seems the same question discussed at https://community.cloudera.com/t5/Support-Questions/Passing-list-of-directories-to-ListHdfs-Processor/td-p/364798 To address the limited number of tables is to limit the number of files in HDFS terms, Listing strategy can only be controlled by File Filter and file-filter-mode on what can be listed. The Listting processing has a two-step -->What to list " controlled by the filter " -->From Whereto list "where in your case looks like sub directory under root has a widespread and number of nested sub dirs are huge where the processor is spending time on recursive searching. If you found this response assisted with your issue, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Chandan

ckumar · ‎02-28-2023

From provided details, It's not clear how the subdirectory structure looks immediately after root directory. The approach could be using multiple ListHDFS configured with an immediate subdirectory of root with recursive subdirectories as true. The flow will look like a Multiple of ListHDFS (Primary )--->All connected to one FetchHDFS (All Nodes ) ith LB at connection. If you found this response assisted with your issue, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Chandan

ckumar · ‎01-18-2023

@jacektrocinski Yes, Sir, you are right, I put more focus on read attribute section of the document which has none but missed seeing Additional details. Kudos!!

ckumar · ‎01-17-2023

ConnectWebSocket does not read any details from Flow file attribute from an incoming flow file. If you are a Cloudera customer, feel free to file a support ticket with us, we should be able to help you on this with a longer engagement. Thank you

ckumar · ‎01-17-2023

Ah my bad, for the WebSocket end point did you try ConnectWebSocket ?

Online	Offline
Last Visited	‎08-28-2025 01:57 AM

Member Since	‎03-10-2017 09:58 AM
Last Visited	‎08-28-2025 01:57 AM
Posts	170
Kudos received	80

Cloudera Community

Re: Data loss(Flow file content) during NIFI Resta...

Re: Schedule Invoking HTTP dynamically - Nifi

Re: Trigger RESTAPI to schedule processors from ni...

Re: Nifi processor missing property

Re: How to consume kafka messages from a specific ...

Re: Connecting nifi to HDFS

Re: Nifi upgrade error: [nifi.sensitive.props.key]...

Re: Nifi upgrade error: [nifi.sensitive.props.key]...

Re: Nifi upgrade error: [nifi.sensitive.props.key]...

Re: Passing list of directories to ListHdfs Proces...

Re: How to list limited number of directories unde...

Re: Passing list of directories to ListHdfs Proces...

Re: NiFi WebSocket Headers

Re: NiFi WebSocket Headers

Re: NiFi WebSocket Headers