Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
Description
The search feature in the ACL picker looks like only searching after the username and not after the other variables (first name, last name, email,...).
Several customers are using obfuscated and unreadable username (e.g: kind of user id with 7 numbers such as the EPFL is doing). It should then be required to be able to search into all the other mounted LDAP properties (or at least the displayed one for ease of understanding of why the search is retreiving such or such user if nothing looks like including the search term).
Ideally speaking mounted LDAP variables should be dynamically mounted in the ACL picker as an option (e.g: click on a column label in order to add the non default but available other user properties)
Screenshot 3: Impossible to know which user is part of a given group without having the rights to go in the admin center and check in the Group Management module.
Editors needs to know the composition of groups by heart or to use an alternative LDAP viewer application near to their Jahia each time they are managing ACL to verify to whom precisely they are granting some privileges on a content object.