@pasq  Did you know that Cloudera makes managing and deploying your MiNiFi agents easy with Cloudera Edge Management?  Our ManagementHub provides a UI to build, deploy and update the dataflow you deploy to one too many MiNiFi agents. You can create parameters for various properties like passwords to provide those at deployment time through Edge Management Check out this Video. NiFi processors with "sensitive" properties are designed to encrypt those password when written to the flow.json.gz.  Even in MiNiFi these component classes will expect that the passwords are encrypted.  The defined sensitive.props.key property value in the minifi.properties or nifi.propertes is used in the encryption/decryption of these sensitive properties stored in the flow.json.gz file. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@Scorpy257 As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

@NaveenSagar Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks. ... View more

@David26  I am not familiar with this specific processor "Plc4xListenRecordProcessor 0.12.0".   I could not find it in Apache NiFi 1.x or 2.x versions.  I could find it in Maven Central either.  Where did you download this nar that you added to your NiFi? What version of Apache NiFi are you using? You may need to reach out to the originator of this custom nar you have added to you NiFi for this processor specific query. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@BuffaloDaddy  What method of user authentication is configured in your NiFi? Single-user ldap-provider Kerberos-provider etc? Thank you, Matt ... View more

HI Matt, Thanks for all your valuable inputs, we configured the SAN disk to nifi cluster based on the above recommendations. Regards Girish V G ... View more

@Darryl  So the downstream system that putUDP is sending to is complaining the size of the datagram is too large when batch size is set to 50.   When using batching in ListenUDP processor each datagram is delimited by a new line character.  You could add a processor like splitText between ListenUDP and PutUDP to split these FlowFiles into smaller FlowFiles before sending to putUDP.  Since a batch size of 30 seemed to work well for you, I would try increasing Batch setting in ListenUDP to 60 and set the "lineSplit Count" in Split text to 30. As far as "When i tried bumping up the concurrent threads from 1 to 2, it caused the video to be extremely blurry", I am guessing maybe the multi-threading is resulting the packets out of order resulting in your extremely blurry video?  If that is the case, you'll need to keep your flow single treaded.  And if order of processing FlowFiles is important downstream connections should be configured with FirstInFirstOutPrioritizer prioritizer.  This does not mean you can then use multiple threads, but makes sure downstream processors take FlowFiles from upstream connections in this order. Please help our community grow and thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@AlokVenugopal  The "/nifi-api/access/token" endpoint is used by the ldap-provider or kerberos-provider NiFi login providers. Since you are using an OIDC (SSO) provider, you would need to obtain the token from that provider.     You can utilize the developer tools available in most browsers to capture the rest-api call being made to NiFi from you browser. While I do not have a setup utilizing Azure AD, I'd expect you should be able to see the redirect to the Azure endpoint to get the token. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt   ... View more

Hi @Shelton Thanks so much for detailed information @MattWho  thanks much for the reply and apologies for short info.  based on above information was able to create SSL certificates and generate Keystore and trustore in jks format . initially i was not configured CA file into truststore so faced some issue 2. then i did not added nifi nodes entries as intial identity in autherizers.xml file so above issue occured . i followed cloudera blogs where you had informed https://community.cloudera.com/t5/Support-Questions/insufficient-permissions-untrusted-proxy/m-p/366443#M239582  based on these i was able to resolve and 3 node cluster with external zookeeper was able to up.  i appreciate your kind help and your time here . much thanks to both 🙂 ... View more