Member since
08-19-2024
40
Posts
8
Kudos Received
1
Solution
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3561 | 08-22-2024 12:41 AM |
06-05-2026
04:08 AM
2 Kudos
@AlokKumar Templates (XML) have been completely removed in Apache NiFi 2.x (including 2.8.0). They are replaced by JSON Flow Definitions. Quick Export/Import (closest to the old template workflow) Export Right-click the Process Group → Download Flow Definition. Choose Without external services (recommended) or With external services. Import Drag a new Process Group from the top toolbar onto the canvas. In the Create Process Group dialog, click the Browse/Upload icon (two boxes with upward arrow) next to the Name field. Select your .json file → Add. Double-click the new Process Group to enter it. Note: Controller Services are not auto-enabled after import — enable them manually. Sensitive properties may need re-entering. Recommended for Production: Use NiFi Registry for versioning and promoting flows across environments. References: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html https://docs.cloudera.com/dataflow/cloud/develop-flow-definitions/topics/cdf-download-flow-definition.html
... View more
06-03-2026
06:06 PM
@AlokKumar You need to make sure each user is authenticating with a unique username in order to know which user made a change If you are using the same user, then all recorded changes will show that single user. Form a pure security standpoint it is a bad practice to have multiple users share authentication credentials. Apache NiFi offers numerous methods for User Authentication. While Lightweight Directory Access Protocol (LDAP) is probably the most commonly used, there are other options to include OpenID Connect, Kerberos, SAML, JSON Web Tokens, and X.509 Client Certificates. If you are currently using the default Single User authentication which the utilizes the Single User authorizer, you will also need to select a different Multi-Tenant Authorization as well to go with the new multi user authentication methods. The most commonly used is the StandardManagedAuthorizer. 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
05-28-2026
10:35 PM
Thank you @steven-matison for suggesting possible solutions. Could you please elaborate as I am new to these terms. I used to have my apis in Java/Spring Boot secured via OIdc/Oauth2 or even Basic for test apis earlier. We used to have libraries in Spring Boot to configure OIDC.
... View more
05-12-2026
05:34 AM
@AlokKumar You can validate the Discovery URL is working by opening it in a browser you should see a JSON document.
... View more
05-07-2026
08:48 PM
@AlokKumar 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
04-06-2026
01:34 PM
@AlokKumar You are correct that the ConsumePOP3 processor does not support an inbound connection to it. Even if it did, the username and password fields do not support NiFi Expression language allowing you to pass either of those values in from the source FlowFile. There aren't any other native processors that can support this dynamic credentials use case. You would need to create a custom script that could be called by scripting processors or create your own custom processor. ExecuteScript ExecuteProcess ExecuteGroovyScript The reason processors like ConsumePOP3 do not support inbound connections is because they are designed to execute continuously on a run schedule and produce an individual FlowFile for each new email message consumed. So supporting an inbound connection raises the question... What do you do with the source FlowFile that you would use as the trigger? Then you also have the challenge of continuously consumption. You would need to keep producing an input FlowFile for each email account to make sure you keep consuming from each source account. Plus this processor does not write any attributes to outbound FlowFile to distinguish which account message came from. 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
10-14-2025
11:41 AM
Hello @AlokKumar, Thanks for using Cloudera Community. As I understand, what you need is to add one more step in your flow: HandleHttpRequest-> MergeContent -> ExecuteScript (Groovy)-> HandleHttpResponse Since you have JSON fields and files, you're getting multiple FlowFiles. So this extra MergeContent phase will combine the JSON and the file into a single FlowFile On the MergeContent, set Merge Strategy as “Defragment” and set Correlation Attribute Name as http.request.id. that is unique from each HandleHttpRequest
... View more
09-26-2025
06:09 AM
1 Kudo
@AlokKumar Did the assistance/information provided in the response(s) to your community question in this thread assist you? Please take a moment to accept the answer that provided the assisting information. Thank you, Matt
... View more
09-26-2025
06:09 AM
@AlokKumar Did the assistance/information provided in the response(s) to your community question in this thread assist you? Please take a moment to accept the answer that provided the assisting information. Thank you, Matt
... View more
09-26-2025
06:08 AM
@AlokKumar Did the assistance/information provided in the response(s) to your community question in this thread assist you? Please take a moment to accept the answer that provided the assisting information. Thank you, Matt
... View more