https://community.cloudera.com/t5/Support-Questions/NiFi-ExecuteScript-alternative-to-InvokeHTTP-processor-Login/m-p/200146#M162177 <A rel="user" href="https://community.cloudera.com/users/1651/menorah84.html" nodeid="1651">@J. D. Bacolod</A><P>Have you considered using the PutDistributedMapCache and GetDistributedMapCache processors?</P><P>Have two separate dataflows. One runs on a cron and is responsible for obtaining the token and write that token to the distirbutedMapCache using the putDistirbutedMapCache processor.</P><P>The Second flow is for doing all your other operations using that token. Just before the invokeHTTP processor add a GetDistibutedMapCache processor that reads the token from the distributed map cache in to a FlowFile attribute. You then use that attribute to pass the token in your connections.</P><P>One thing to keep in mind is that it is possible that a new token may be retrieved after a FlowFile had already retrieved the old token from the distirbutedMapCache. This would result in auth failure. So you will want your flow to loop back to GetDistributedMapChace processor to get latest key on auth failure on your invokeHTTP processor.</P><P>This flow does not keep track in any way when a token expires, but if you know how long a token is good for you can set your cron accordingly.</P><P>Thanks,</P><P>Matt</P> Wed, 07 Jun 2017 21:29:33 GMT MattWho 2017-06-07T21:29:33Z