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

Juan Pablo Converso commented on NIFI-5948:
-------------------------------------------

Thanks for the message!
Yes I'm using the LDAP provider to list users and the file-based provider to 
define groups.
The reason of this configuration is that we want the IT department to give 
access or not to Nifi and then we want to define groups inside Nifi to 
determine which user will have access to which features.
I've uploaded my current configuration files in the JIRA (authorizers.xml, 
login-identity-providers.xml and nifi.properties)

> Cannot list users when a ldap user that belongs to a group is deleted
> ---------------------------------------------------------------------
>
>                 Key: NIFI-5948
>                 URL: https://issues.apache.org/jira/browse/NIFI-5948
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>    Affects Versions: 1.8.0
>            Reporter: Juan Pablo Converso
>            Priority: Major
>         Attachments: authorizers.xml, error.png, 
> login-identity-providers.xml, nifi.properties
>
>
> I configured Nifi to use LDAP to provide users. Then in Nifi, using the UI, I 
> created groups and associated some LDAP users to the groups.
> This worked fine until a user was deleted in LDAP, when this happened when I 
> tried to list users using the "burgerMenu -> Users" option the error: "Unable 
> to find user with id 'ae1523b4-1336-3a1c-8283-0a784f5cb017'." was displayed.
> The only way to fix this problem was to delete the association of the user to 
> the group in the file: users.xml.
> I think that when a user is deleted from LDAP and Nifi refreshes the user 
> list it should check also for deleted users in order to remove them from 
> user/groups associations as well to prevent this problem.
> I've provided in this report a screenshot of the error.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to