@KD9   How long the NiFi server will validate a clients token is configured within the login-identity-providers.xml file via the following property: Authentication Expiration When setting up an automated process, using client tokens is not the best method.  A better option would be to authenticate your client via a client certificate.   With a client certificate, there is not need to obtain a token.  That Client certificate will continue to work for the life of the certificate (certificates do have a valid until date set when you generate the certificate).   So instead of passing a bearer token in your curl command, you would use your client pem key.   The owner DN from the client certificate would be used as the user identity that you would then need to authorize in NiFi for the rest-api endpoint(s) needed for your automation. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@ImranAhmed If I am understanding you correctly, you are trying to verify the content has correctly been modified before it is written out via your invokeHTTP processor.Inspecting that your dataflow is working as expected.  If you stop your InvokeHTTP processor after the ReplaceText processor, the FlowFile processed by the ReplaceText will queue in the connection.  You can then right click on the connection and list the queue.  From there you can view/download the content of that FlowFile post ReplaceText to verify it contains the expected modified content before the InvokeHTTP is started and writes it to your DB.   Thanks, Matt ... View more

@arkumari 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. ... View more

Hi @neeraj_sha , have you implemented this requirement, if so can you please share your solution?   ... View more

@winbob, 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.   ... View more

@Matt    thank you very much for all the answer.   We are still insisting on getting the Base64 field from Oracle because the PDF is already there. I'm using the Base64EncodeContent process to decode the Base64 field coming from Oracle.   I was able to send a file to the E-mail with PDF format, but it still has an error when opening the PDF file sent in the E-mail.   It seems to me that Nifi cannot say that the code it is decoding from the Base64 field that is coming from Oracle. Sorry for the lack of knowledge on the subject.       ExecuteSQL   UpdateAttribute   Base64EncodeContent   PutEmail    PutEmail    ... View more

@prparadise  The NiFi MergeRecord assigns queued FlowFile on inbound connections to bins.  Bins can only contain "like FlowFiles". In order for two FlowFiles to be considered 'like FlowFiles', they must have the same Schema (as identified by the Record Reader) and, if the <Correlation Attribute Name> property is set, the same value for the specified attribute. Initial thoughts: 1. Perhaps your source FlowFiles are resulting in unique inferred schemas. The XMLRecordSetWriter can be configured with a schema write strategy such as "Set 'avro.schema' attribute" so that the output merged FlowFile has the schema added to an attribute (this would allow you to see the inferred schema on multiple FlowFiles to see if they match. 2. The min number of records per bin is set to 1 still.  When the Merge type processors execute that look at an inbound connection and allocate queued FlowFiles to bin(s).  At end of binning, it will see if any bin is eligible for merge. This processor can execute very fast and frequently.  Let's say that each time it executes, the inbound connection only contains 1 FlowFile. Since  min records per bin is 1, a bin with only one FlowFile would get merged.  Try setting the min records to a higher value.  Whenever you change the "min" settings, you should also set the "Max Bin Age" property.  This forces a bin to merge after the configured amount of time even if min values are not met. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

@myzard  Did your LDAP manager password contain any XML special characters? Did you verify ldapsearch worked from same same host were NiFi is installed using that manager DN and Manager password to get a return for the user you are trying to login in with? what output did you get from ldap search? For the ldap-provider, there are only two username and passwords in use: 1. Manager DN and Manager password configured in the ldap-provider 2. username and password entered at login interface. Other suggestions: - Make sure there are no leading or trailing whitespaces on the username or password configured in the provider or entered at the login windows. - Make sure the nifi.properties file is properly configured for the ldap-provider and not a different login provider like kerberos-provider. - Share you ldap-providers.xml file Thanks, Matt ... View more