https://community.cloudera.com/t5/Support-Questions/NIFI-quot-No-available-buckets-quot-for-saving-flow-version/m-p/326155#M229790 <P>I know this post is rather old and probably no longer of interest for the original user, but as I faced the same or similar issue today and as it took me round about two hours to finally have a docker container with a running secured nifi-registry setup, I wanted to share what I was missing:</P><P>&nbsp;</P><P>Besides the admin user for the registry, one must create at least *two* additional users in the registry.</P><P>One user must match the running secured NiFi certificate issuer exactly (capital/lowercase and spaces) like: `CN=nifimain, OU=NIFI`. This one needs the general "Can proxy user requests" rights. The other user created must match exactly the user you use to login into your NiFi web UI. This should usually be another certificate issuer. In my case on local testing only, I setup a single-user-provider as authentication mechanism and chose `admin` as the username, so in the registry, I had to create a user called `admin` which I granted an access policy to the bucket I wanted to be able to read.</P><P>Only with both of the users setup, I was able to see my bucket listed in the NiFi ui and start version control.</P> Sun, 03 Oct 2021 15:48:44 GMT Theoo 2021-10-03T15:48:44Z