About MattWho

MattWho · ‎11-02-2023

@jai1gupta What makes you think your NiFi is not secured over https? You did not share your nifi.properties web properties. If you have set the following properties: nifi.web.https.host=<hostname> nifi.web.https.port=<port> and have configured the NiFi keystore and truststore properties (which you did share), the your NiFi would have started at logged url being available over HTTPS://<hostname>:<port>/nifi My guess is your issue probably extends from the use of "localhost" instead of an actual resolvable hostname. If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

MattWho · ‎11-02-2023

@samrathal Apache NiFi has hardcoded return size to 100: https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/dao/impl/StandardConnectionDAO.java#L361 I am sure this was originally done for performance and NiFi JVM heap usage reasons. The first 100 returned should be the oldest 100 in queue (keeping in mind that a connection will also show count of FlowFiles pending processing by downstream processor and count of those currently allocated to a downstream component process. The listing only returns those pending FlowFiles and not those already owned by downstream component).What is the use case for needing to list more? Ideally what is found in a queue should be changing rapidly, so expectation is that each listing request would be different. Listing a queue does not stop NiFi processing. The intent is not for NiFi to ever hold FlowFiles in any connection. So using API to poll connection for FlowFile listings seems odd to me. What is returned by that listing could be inaccurate milliseconds later. Also be careful with your API requests. When a listing is performed through the browser three different request are made. 1. First listing-request is made and replicated to all nodes to get result sets. 2. Return from step 1 request gives the ID for the generated listing request being held in heap memory. That ID is used to fetch the results in that specific listing ID 3. A DELETE request is made to remove the listing with that ID from NiFi. *** When using API, If steps 1 and 2 are all that are being executed, the various listing request(s) will stay in heap memory. If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

MattWho · ‎10-31-2023

@plapla The DistributedMapCacheClientService is used to connect to the DistributedMapCacheServer. You have not shared how you have the DistributedMapCacheServer controller service configured. The DistributedMapCacheServer configuration determines whether the DistributedMapCacheClientService needs tobe configured with a StandardRestrictedSSLContext Service. Essentially if you configure a StandardRestrictedSSLContext service on the DistributedMapCacheServer, then it must also be configured on the DistributedMapCacheClientService. If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

MattWho · ‎10-30-2023

@Madhav_VD Apache NiFi is data agnostic which makes it possible to ingest data of any format. It does this by wrapping the bytes of data in to a NiFi FlowFile. The only thing time the content (data bytes) are read from the FlowFile would be by a NiFi processor component that would need to do so. And only a processor specifically designed to handle the specific content type of the data would be able to do anything with the FlowFile content. That being said, NiFi had no Content conversion processor capable of reading FFmpeg content format and writing out TIFF content format. So the question here is how woudl you accomplish the format conversion outside of NiFi? Perhaps this thread would help you there: https://superuser.com/questions/881783/convert-from-avi-to-uncompressed-tiff-using-ffmpeg NiFi in this case could still be used to automate the ingestion and conversion of your FFmpeg files by utilizing perhaps one the NiFi Scripting processors like ExecuteGroovyScript or ExecuteScript (where you can create a custom script that has some dependency on client libraries capable of doing the conversion) or maybe the ExecuteStreamCommand or ExecuteProcess processor that could call a local command line command that you pass the FlowFile content to and returns a content stream with the new Tiff format? If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

MattWho · ‎10-30-2023

@jai1gupta Yes NiFi out-of-the-box in the latest releases is secured to run over HTTPS. However, that out of the box default setup is very basic (non production setup) to allow users to work within a secured NiFi. Its default setup utilizes the Single-User-Provider authentication login provider (configured in login-identity-providers.xml) and single-user-authorizer configured in the authorizers.xml. This out-of the-box provider does not support multi-user capability. For multi-user production ready deployments with ability to define very granular access controls, you'll need to use a different authentication provider (Most commonly used is probably the ldap-provider) and different authorize (most commonly used is the StandardManagedAuthorizer configured to use the file-user-group-provider and file-access-policy-provider). NiFi does not offer any built in multi-user provider that allows you to create local to NiFi users with passwords. keeping above in mind, you are trying to use the OpenID authentication method. This still means you must be using a different Authorizer. The single-user-authorizer can only be used with the Single-user-provider. More detail around your setup, OpenID exceptions, etc is needed to help here. If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

MattWho · ‎10-30-2023

@AhmedParvez Of course digging in to why the connections are failing and addressing that is always going to be the best option rather then building work arounds like this. MY suggestions should be used a method to sustain operations while working on the correct solution. Perhaps that solutions means contributing to improvements to these MQTT processors or identifying deficiencies in these Processors and then raising detailed Apache NiFi jira tickets in the community to improve them.

MattWho · ‎10-27-2023

@plapla This is a completed unrelated issue to the question in this thread. To avoid confusion within the community we should keep unrelated queries in different posts. Please start a new community question for this new query. Fee free to use @MattWho in your new question so i get notified about it. Thank you, Matt

MattWho · ‎10-26-2023

@jai1gupta For Browsers like Chrome that are integrated with Apple Mac Keychain access, you will want to convert that p12 in to a cer and then import the cer. openssl pkcs12 -in CN=admin_OU=lending.p12 -clcerts -nokeys -out CN=admin_OU=lending.cer Then try importing the cer file that above output in to keychain access. If you have Firefox installed on your Apple Mac, then you could launch Firefox ---> preferences --> Privacy & Security (scroll down to "Security" section) --> click "View Certificates" --> select "Your Certificates" --> then click "Import" (select your p.12 file). If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt

MattWho · ‎10-26-2023

@jai1gupta I am not clear on your ask here and it does not seem related to the question asked and solution accepted in this thread. Please start a new community question with details around what you are trying to accomplish/solve. Feel free to @MattWho in that new question so that I get notified and I will try to assist you there. Thank you, Matt

Barsha · ‎10-25-2023

This indeed solved the problem. Thanks a lot for your support.

Online	Offline
Last Visited	‎11-19-2025 11:37 PM

Member Since	‎07-30-2019 10:41 AM
Last Visited	‎11-19-2025 11:37 PM
Posts	3,391
Kudos received	1614

Cloudera Community

Re: How to achieve inheritence within Parameter Co...

Re: Cannot access the NiFi Registry from NiFi and ...

Re: Error connecting to NiFi Registry from NiFi UI...

Re: using nifi as a kafka streaming- real-time str...

Re: using nifi as a kafka streaming- real-time str...

Re: trying to authenticate nifi with openID using ...

Re: How to retrieve a complete list of flowfiles i...

Re: Apache Nifi 1.23.2 FetchDistributedMapCache Co...

Re: How to use FFmpeg in NIFI?

Re: Apache NiFi user authentication + creation of ...

Re: Nifi and IOT hub connectivity breaks intermitt...

Re: Nifi flowFile content changes spontaneously

Re: failed at uploading .p12 certificate in keycha...

Re: How to set passwords for multiple users in Apa...

Re: Flowfile contents are corrupted after upgradin...