[ 
https://issues.apache.org/jira/browse/NIFI-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077057#comment-16077057
 ] 

ASF GitHub Bot commented on NIFI-4127:
--------------------------------------

Github user pvillard31 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/1978#discussion_r125983064
  
    --- Diff: nifi-docs/src/main/asciidoc/administration-guide.adoc ---
    @@ -464,6  464,17 @@ Another option for the UserGroupProvider is the 
LdapUserGroupProvider. By defaul
     * Group Name Attribute - Attribute to use to extract group name (i.e. cn). 
Optional. If not set, the entire DN is used.
     * Group Member Attribute - Attribute to use to define group membership 
(i.e. member). Optional. If not set group membership will not be calculated 
through the groups. Will rely on group member being defined through 'User Group 
Name Attribute' if set.
     
     Another option for the UserGroupProvider are composite implementations. 
This means that multiple sources/implementations can be configured and 
composed. For instance, an admin can configure users/groups to be loaded from a 
file and an directory server. There are two composite implementations, one that 
supports multiple UserGroupProviders and one that supports multiple 
UserGroupProviders and a single configurable UserGroupProvider.
     
     The CompositeUserGroupProvider will provide support for retrieving users 
and groups from multiple sources.
    --- End diff --
    
    I think we should indicate that if we have users/groups collisions between 
the sources, NiFi won't start successfully.


> Create a CompositeUserGroupProvider
> -----------------------------------
>
>                 Key: NIFI-4127
>                 URL: https://issues.apache.org/jira/browse/NIFI-4127
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Gilman
>            Assignee: Matt Gilman
>
> Create a CompositeUserGroupProvider to support loading users/groups from 
> multiple sources. This composite implementation should support
> {noformat}
> 0-1 ConfigurableUserGroupProvider
> 0-n UserGroupProviders
> {noformat}
> Only a single ConfigurableUserGroupProvider can be supplied to keep these 
> sources/implementation details hidden from the end users. The 
> CompositeUserGroupProvider must be configured with at least 1 underlying 
> provider.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to