[
https://issues.apache.org/jira/browse/NIFI-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596257#comment-16596257
]
ASF GitHub Bot commented on NIFI-5542:
--------------------------------------
Github user kevdoran commented on the issue:
https://github.com/apache/nifi/pull/2970
Ok, thanks @pepov -- that clears up the intention of these changes to me.
For naming of variables/properties I'm good with either _identity_ or
_name_, as you suggest - both are clear to me and distinct from _identifier_. I
was more concerned with the usage of the method
`UserGroupProvider.getGroup(String groupIdentifier)`, which will will have to
change if the value is not actually an identifier.
For accessing users, the
[UserGroupProvider](https://github.com/apache/nifi/blob/master/nifi-framework-api/src/main/java/org/apache/nifi/authorization/UserGroupProvider.java)
interface provides both `getUser(String identifier)` and
`getUserByIdentity(String identity)` methods. I don't see an equivalent method
for groups that is a lookup by name/identity, so you'll have to work around
that.
> Add support for node groups to FileAccessPolicyProvider
> -------------------------------------------------------
>
> Key: NIFI-5542
> URL: https://issues.apache.org/jira/browse/NIFI-5542
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Andrew Christianson
> Priority: Major
>
> Currently in FileAccessPolicyProvider, it is possible to specify a set of
> node identities, which are given access to /proxy. This works well for static
> clusters, but does not work so well for dynamic clusters (scaling up/down #
> of nodes) because we don't know in advance what the node identities will be
> or how many there will be.
> In order to support dynamic sets of node identities, add support for
> specifying a "Node Group," for which all identities in the group will be
> granted access to /proxy. A UserGroupProvider can then be implemented to
> gather node identities dynamically from the cluster environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
