| Summary | Allow user to choose LDAP Field to match in group membership |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | No Feedback |
| Priority | 2. Medium |
| Owners | |
| Requester | lorenzettoluca (at) provincia (dot) treviso (dot) it |
| Created | 09/07/2011 (5064 days ago) |
| Due | |
| Updated | 02/11/2016 (3446 days ago) |
| Assigned | |
| Resolved | 02/11/2016 (3446 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Feedback
Version ⇒ Git master
group member attribute. Isn't that sufficient?
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ Allow user to choose LDAP Field to match in group membership
Type ⇒ Enhancement
State ⇒ New
The users logs in with in the first case the sAMAccountName field, in
the second case the email address. But nobody is set as member of
groups because the name retrieved by the membership function of horde
does not match with the horde username.
The group members listed on the Group section is the name of the
object in LDAP, which in my case is or the CN of the Object if set the
flag in the option, or the complete object name from AD.
I think will be useful to allow user to decide how to match horde
usernames in LDAP objects, specially for users like me that are
integrating Horde with Active Directory.