About MattWho

MattWho · ‎06-29-2021

@data-light NiFi nodes will always be authenticated via the clientAuth certificate they present. The Owner DN from the node's PrivateKeyEntry in the keystore file is what is used. What is important to know is that NiFi provides a mechanism that can trim/modify those full DNs through the uses of identity mapping properties [1]that users can configure in the nifi.properties file. After a mapping is applied against an identity string the resulting mapped value is what is actually passed to the configured NiFi Authorizer. So within the authorizer, that now mapped value is what the authorization policies need to be mapped to. The nifi-user.log will show the mapped value (case sensitive) that is being used during authorization. So if you see only "Nifi-node-0" in the nifi-user.log, then that exact string is what needs to exist in your authorizer and have policy assigned to it. If the nifi-user.log was showing "cn=Nifi-node-0, ou=mycompany, ou=nifi", then that full DN would need to be present in your authorizer with assigned policies. So you will want to get a verbose output of your nodes keystore files, your nifi.properties file to see what identity mapping patterns have been set, and the authorizers.xml to see how your authorization setup is done, and the nifi-user.log. [1] https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#identity-mapping-properties Hope this helps address your question. IF so, please take a moment to login and click "Accept" on this solution. Thank you, Matt

Mahi123 · ‎06-24-2021

@MattWho Thank you so much for responding, I want to rename the outgoing file as such "name_timestamp". want to name each file with the following standard "name"+"_"+"timestamp" and the issue is solved after changing destination value from flowfile-content to flowfile-attribute initially it was pointing to flowfile-content and I dont see the custom extracted attributes in attribute section, but after changing to flowfile-attribute, I can see the extracted values in the attribute section thank you very much

MattWho · ‎06-24-2021

@midee I just ran the test myself with your sample as a one line formatted json and it still worked. {"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations","id": "1155391","key": "DPGAUT-2","fields": {"customfield_10001": null,"customfield_10002": null,"customfield_10003": null,"customfield_10004": null,"customfield_10005": null,"customfield_10006": null,"resolution": null,"customfield_10101": "","customfield_10007": null,"customfield_10008": null,"customfield_10009": "This is required value","customfield_10010": null,"customfield_10011": null,"customfield_10012": null,"customfield_10013": null,}} Make sure your RouteOnContent processor dynamic property value does not have a line return in it. You'll notice it only shows "1" line above. If you see a "2" line then you have a line return in your Value field which would cause the issue you are seeing. Hope this helped, Matt

Wynner · ‎06-21-2021

@ubetThe path to java.exe cannot have a blank space.

bhavya · ‎06-20-2021

Yeah!I want to execute the SQL file and convert into Json But I'm not getting how to do as I'm at first level of learning.

Ash1 · ‎06-16-2021

Thanks you very much Matt .. this definitely helped a lot .

MattWho · ‎06-15-2021

@Arash The "nifi.remote.input.socket.port" property is used so that the receiving NiFi can support the RAW transport protocol. This port has nothing to do with where within your dataflows the transferred data is being ingested. The Remote Process Group (RPG) that exists within your MiNiFi dataflow acts as a client. It will execute a background thread every 30 seconds that connects to the target NiFi URL configured in the RPG that fetches NiFi Site-To-Site (S2S) details from the target NiFi. These S2S details include details about the target. This information includes but is not limited to the following: 1. Hostnames of all nodes in target NiFi cluster 2. Remote (RAW) input socket port if configured 3. FlowFile load on each cluster node 4. Remote input and output ports this client is authorized access to. There is no option to configure multiple remote input socket port values. RPG would not know how to use them even if there was. In your case each unique MiNiFi should have be pushing to a different Remote input port on the canvas instead of all of them sending to same input port. Second option is to use a RouteOnAttribute processor after your single Remote input port that routes data based on the "s2s.host" attribute value set on the received FlowFiles. This attribute is set by the sending RPG on each MiNiFi to the hostname of that MiNiFi. You could of course also set a unique attribute on each FlowFile via na UpdateAttribute processor on each MiNiFi also before sending through the RPG. If you found this addressed your query, please take a moment to login and click "Accept" on solutions that helped you. Thank you, Matt

mescal · ‎06-14-2021

Hi Leopol, Hope I understand your needs. You may try using compressContent processor instead of UnpackContent, select uncompress mode and choose the compression format.

myuintelli2021 · ‎06-14-2021

@VidyaSargur We have not resolved the issue yet due to some priority shift. We're still seeing the same error. Will follow up on it soon. Ming

MattWho · ‎06-14-2021

@Justee The ExecuteProcess [1] processor by design does not allow an inbound connection. It is designed to create an output FlowFile and does not except a FlowFile as input. You can connect getFile to the ExecuteStreamCommand [2] processor [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache.nifi.processors.standard.ExecuteProcess/index.html [2] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html

Online	Online
Last Visited	‎02-05-2026 08:59 AM

Member Since	‎07-30-2019 10:41 AM
Last Visited	‎02-05-2026 08:59 AM
Posts	3,436
Kudos received	1628

Cloudera Community

Re: Setting TTL per key when writing to redis

Re: Best Practice for configuring registry flows

Re: Nifi 2.7.2 Start Problem

Re: Error importing NiFi workflow template from ve...

Re: nifi 2.6 registry security scan results

Re: I cannot see the data in the queue, I'm in Nif...

Re: Hi, question in nifi updateattribute processor

Re: To loop through the dataflow

Re: Apache nifi registry in windows 10

Re: Convert an SQl file from Mysql to JSON file in...

Re: How to fetch files form a SFTP location with n...

Re: Multiple Values for Nifi.Remote.Input.Socket.P...

Re: [Apahe Nifi] Module UnpackContent

Re: Nifi untrusted proxy caused by Untrusted Proxy...

Re: Combine GetFile and ExecuteProcess