@RalphA @udayAle  I encourage you to raise your question as a new question in Cloudera Community rather then asking your question as a comment on an existing article.  You can certainly. reference this article in your new community question.  You'll get better visibility that way to you query. Thank you, Matt ... View more

@Kiranq  1. What version of NiFi and NiFi-Registry are you using? 2. How is your GitFlowPersistenceProvider configured? Matt ... View more

@MOUROU  Is your NiFi configured to support Oauth2 based user authentication? It looks more like you are using either kerberos-provider or ldap-provider fro user authentication. My suggestion to create a client certificate and use a SSLContext service for client authentication for an automated dataflow like this is because: 1. No need to obtain an token ever. 2. Certs can be created with long expiration time. 3. Tokens are NiFi node specific (same token is not valid for a different NiFi node in a the same NiFi cluster). 4. Same certs works no matter which node in the cluster the invokeHTTP connects with. Matt ... View more

@MOUROU  I'd recommend using a clientAuth certificate fro interacting with the NiFi rest-api.  Certificate based authentication via a mutualTLS exchange (always enabled in a secure NiFi) is already how NiFi nodes communicate with one another.  Using certificate does not require the extra step if obtaining a token,  Token is only valid for use with the NiFi node that issues it.  Certificated can be created with long expiration times (typically valid for 1 or 2 years by default) 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

@steven-matison  Looking at your flow-definition, I see that your invokeHTTP processor are configured to use an SSLContextService.  I am assuming that SSLContextService is configured with the HTTPS enabled NiFi keystore and Truststore.   When you then access the https rest-api endpoint, NiFi in the TLS exchange WANTs a client certificate which would be provided via the SSLContextService.  I am then guessing your NiFi servers have been authorized to access that rest-api endpoint. You are correct that you would not need an Access Token since authentication was handled via a mutual TLS exchange with NiFi.    Using certificates is actually the recommend method for interacting with the NiFi rest-api for a number of reasons: - No need for extra step to get a token. - Token is only valid for the specific NiFi node that issued it. Thanks, Matt ... View more

@noncitizen  Welcome to the Community!!! Apache NiFi is a very large open source project.  Over the 8+ years since it was originally open sources it has grown so large that the download distribution has reached the max allowable size and does not include all components that the community has developed for NiFi.  There are more then 400+ unique components developed for NiFi and growing every year.  Many of these "add-on" components can be found in various open source repositories and NiFi makes it every easy to add them to your NiFi (even hot loading is possible).   As is true with many open source products with lots of contributors, the documentation usually comes after the development and may at times be lacking in detail.  Sometimes this because the originator could not anticipate all the possible use cases for a given component or being so close to the development there is good amount of self inferred knowledge and understanding.  I myself have been working with NiFi for more then 8 years and have been exposed to many use cases, bugs, improvements, etc.   I look forward to seeing you more in the community as you learn and grow and begin to help others using that new found knowledge. ... View more