[
https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863492#comment-16863492
]
Andrew Lim edited comment on NIFIREG-284 at 6/14/19 4:05 PM:
-------------------------------------------------------------
Per a discussion with [~bende], for 0.5.0 migration guide, should note:
Existing registries will have NiFi nodes as Proxy with WRITE, so on upgrade
admins will need to go in and add READ and DELETE to get them back to the same
functionality they had before.
For _new_ installs this is not an issue because any NiFi Identities listed in
_authorizers.xml_ will be granted all three.
was (Author: andrewmlim):
Per a discussion with [~bende], for 0.5.0 migration guide, should note:
Existing registries will have NiFi nodes as Proxy with WRITE, so on upgrade
they need to go in and add READ and DELETE to get them back to the same
functionality they had before
For new installs it is fine because any NiFi Identities listed in
_authorizers.xml_ will be granted all three.
> Update docs for newly added granular proxy policies
> ---------------------------------------------------
>
> Key: NIFIREG-284
> URL: https://issues.apache.org/jira/browse/NIFIREG-284
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Andrew Lim
> Assignee: Andrew Lim
> Priority: Major
> Labels: migration
>
> Read/write/delete policies added via NIFIREG-212
> At minimum, need to update screenshots as a result. But can also add more
> information for possible use cases with these policies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
