<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Nifi not able to load available buckets in nifi registry in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Nifi-not-able-to-load-available-buckets-in-nifi-registry/m-p/330325#M230645</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/93216"&gt;@Yemre&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Authorizing your user is not enough.&lt;BR /&gt;The NiFi nodes themselves need to be able to successfully authenticate via a mutual TLS handshake with the target NiFi-Registry.&amp;nbsp; Those nodes then need to be authorized to read all buckets and given read/write to proxy user requests.&lt;BR /&gt;&lt;BR /&gt;When a User authenticates in to NiFi, that user entity is authorized to perfrom actions based on authorizations in NiFi. When it comes to NiFi then talking to NiFi-Registry, The NiFi node is proxying request to the NiFi-Registry on behalf of the user authenticated into NiFi.&lt;BR /&gt;&lt;BR /&gt;Also background threads in NiFi just like the NiFi processors added to the canvas are not executing as the user authenticated in to NiFi.&amp;nbsp; So in the background NiFi connects to NiFi-Registry to check on current version controlled process groups to see of newer versions exist.&lt;BR /&gt;&lt;BR /&gt;While you are granting your NiFi nodes the ability to read all buckets, the NiFi users should be given read and write authorizations to the specific buckets that that user is going to sue to version control their Process Group.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/93216"&gt;@Yemre&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ability to dynamically fetch secrets/passwords form an external source is not something that exists currently. Doing so would require modification with the every component class that uses sensitive properties.&lt;BR /&gt;&lt;BR /&gt;There is some progress in this path however:&lt;BR /&gt;&lt;A href="https://issues.apache.org/jira/browse/NIFI-5481" target="_blank"&gt;https://issues.apache.org/jira/browse/NIFI-5481&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This new feature handles pulling secrets from an external vault, but is a NiFi core level feature and does not extend in to individual flow component level.&lt;BR /&gt;&lt;BR /&gt;I recommend raising an Apache NiFi Jira with your specific request.&amp;nbsp;&lt;BR /&gt;&lt;A href="https://issues.apache.org/jira/projects/NIFI/" target="_blank"&gt;https://issues.apache.org/jira/projects/NIFI/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If you found this response assisted with your query, please take a moment to login and click on "&lt;STRONG&gt;Accept as Solution&lt;/STRONG&gt;" below this post.&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Tue, 16 Nov 2021 14:20:36 GMT</pubDate>
    <dc:creator>MattWho</dc:creator>
    <dc:date>2021-11-16T14:20:36Z</dc:date>
  </channel>
</rss>

