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

ASF GitHub Bot commented on NIFIREG-109:
----------------------------------------

GitHub user kevdoran opened a pull request:

    https://github.com/apache/nifi-registry/pull/82

    NIFIREG-109 Expand LdapUserGroupProvider Config

    Expands on user-group configurability by allowing a referenced
    user or group attribute to be specified when determining group
    membership. Updates corresponding documentation. Adds test cases.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kevdoran/nifi-registry NIFIREG-109

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/82.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #82
    
----
commit c937399c9cef317ec6f4139feeb037d7b2dc0cea
Author: Kevin Doran <kdoran.apache@...>
Date:   2018-01-09T22:08:59Z

    NIFIREG-109 Expand LdapUserGroupProvider Config
    
    Expands on user-group configurability by allowing a referenced
    user or group attribute to be specified when determining group
    membership. Updates corresponding documentation. Adds test cases.

----


> LdapUserGroupProvider: Allow admin to configure group membership attribute
> --------------------------------------------------------------------------
>
>                 Key: NIFIREG-109
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-109
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Kevin Doran
>            Assignee: Kevin Doran
>             Fix For: 0.1.1
>
>
> This is a cloned issue from NiFi (NIFI-4567) that is also relevant in NiFi 
> Registry as it uses the same LDAP configuration functionality.
> Currently, group membership is defined using a fully qualified DN between 
> user and group or between group and user. When membership is defined through 
> a user, the group DN is required. When membership is defined through a group, 
> the user DN is required.
> We should add another property to configure which attribute in the referenced 
> group or user should be used as the value of the user's group attribute or 
> the group's user attribute. For instance, if the user's member attribute 
> contains the value 'group1' this new property would be the group attribute 
> that returns the value 'group1'. When these new properties are blank a full 
> DN is assumed.



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

Reply via email to