Greetings, and thanks for great work!
We're trying to setup the secured NiFi Registry. Logins are synchronized from AD, while policies are stored in authorizers.xml. We've created a bunch of users in NiFi and added them to the "Administration" group, then copied users.xml to NiFi Registry and (from the initial admin identity) activated all policies on this group, including user management. However, members of this group still aren't able to add users themselves. Is this a bug, or some misconfiguration on our side?
upd: looks like the problem is deeper. We've added another user (through the initial admin identity) with explicitly added "user access". However, he is still not able to create new users and/or manage existing ones. What should we check, then?
upd2: after writing the previous text, I've refreshed the NiFi Registry page, and "Add user" button became active. Magic...
... View more
We're using the NiFi Registry to store our flows. Some of them have subgroups inside them, with variables defined on that subgroups, - the thought was that this subgroups will be reusable with only these variables changing. I.e., the structure is of the following shape: group under version control
|-subgroup A |-variable with value A1
|-subgroup A |-variable with value A2 We don't want to store these subgroups under version control too, because it would be just too much work. But the problem is that, when we change the values A1 and A2 and commit the top group, the subgroup variables aren't updated in registry, we have to delete the whole registry entry and recreate it from scratch. Is this the correct behaviour?
... View more