https://community.cloudera.com/t5/Support-Questions/NIFI-quot-No-available-buckets-quot-for-saving-flow-version/m-p/308405#M223533 <P><a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/84026">@JelenaS</a>&nbsp;<BR /><BR />You are correct that this sounds like an authorization issue.<BR /><BR />I recommend tailing the nifi-registry-app.log&nbsp; and then perform the action of trying to version control a Process Group within NiFI's UI.<BR /><BR />How are you handling user authorization in your NiFi and NiFi-Registry?<BR />- File based authorization (users.xml and authorizations.xml)<BR /><BR />What identity.mapping patterns have you configured in your NiFi and NiFi-Registry?<BR />How are you authenticating your user that access both NiFi and NiFi-Registry?<BR /><BR />The only buckets that would be returned are those buckets for which the Authenticated user in NiFi has access to in NiFi-Registry.<BR /><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2020-12-23 at 3.43.29 PM.png" style="width: 751px;"><img src="https://community.cloudera.com/t5/image/serverpage/image-id/29935i10E9984A567431A3/image-size/large?v=v2&amp;px=999" role="button" title="Screen Shot 2020-12-23 at 3.43.29 PM.png" alt="Screen Shot 2020-12-23 at 3.43.29 PM.png" /></span><BR /><BR /></P><P>Keep in mind that the user/client strings in NiFi that are passed to NiFi-Registry must match exactly.<BR /><BR />Nodes will pass their full DN when they proxy the request on behalf of the authorized user.&nbsp; The user string will passed as is.&nbsp; &nbsp;That means identity mapping patterns will be applied on NiFi-Registry side against those NIFi DNs.&nbsp; Resulting mapped value must match the client string add as a user in NiFi-Registry.<BR /><BR />The passed user string must match exactly (case sensitive) or it is treated as a different user.</P><P>&nbsp;</P><P>Hope this helps,</P><P>Matt</P><P>&nbsp;</P> Wed, 23 Dec 2020 20:48:09 GMT MattWho 2020-12-23T20:48:09Z