Sarah Olson also points out that the Migration Guidance [1] on the same wiki is 
much more up to date and includes notes about the authoriz* and users.xml files.

[1] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance 
<https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance>

Andy LoPresto
[email protected]
[email protected]
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On May 2, 2018, at 1:00 PM, Andy LoPresto <[email protected]> wrote:
> 
> Hi Ryan,
> 
> Yes, it appears that document is out of date. Thanks for pointing this out. 
> The NiFi Admin Guide [1] has current information on how to manage access 
> controls via the new files.
> 
> The state directory stores valuable data for cluster coordination and other 
> features but is not related to user access control.
> 
> Do you have a specific question with regards to performing your upgrade? 
> Hopefully we can help.
> 
> If you can, please open a Jira to update this documentation.
> 
> [1] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#multi-tenant-authorization
>  
> <https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#multi-tenant-authorization>
> 
> Andy LoPresto
> [email protected] <mailto:[email protected]>
> [email protected] <mailto:[email protected]>
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> 
>> On May 2, 2018, at 11:48 AM, Ryan H <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi,
>>    Are there updated NiFi docs for upgrading NiFi's that have the new access 
>> controls?  eg. 1.3 -> 1.4 or 1.4 -> 1.6?  There looks like a couple more 
>> files that need to be moved over... users.xml, authorizations.xml.. I copied 
>> over the state folder (although I'm not sure if I had to)
>> 
>>    I'm looking here:  
>> https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi 
>> <https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi>
>> 
>> Thanks,
>> Ryan
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to