6.0.0-alpha12
6/7/25

[#4699] Broken LDAP group management functionality
Summary Broken LDAP group management functionality
Queue Horde Base
Queue Version 3.1.3
Type Bug
State Resolved
Priority 1. Low
Owners ben (at)
Requester ray (at) skyblue (dot) pty (dot) st
Created 11/27/2006 (6767 days ago)
Due
Updated 06/29/2007 (6553 days ago)
Assigned 06/13/2007 (6569 days ago)
Resolved 06/29/2007 (6553 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
06/29/2007 10:15:56 PM Jan Schneider Comment #3
State ⇒ Resolved
Reply to this comment
No feedback.
06/13/2007 11:19:13 PM ben State ⇒ Feedback
 
06/13/2007 11:18:54 PM ben Comment #2 Reply to this comment
1.  The ldap_sort function appears to sort in alphabetical order, so
the _nextGid method in the Group_ldap class often returns gidnumbers
that already exist in the directory.
Committed, thanks!
2. In the group configuration for my horde installation, I set the
base DN as ou=Group,o=SB. When I create new groups, it appears that
the LDAP_Group method in the LDAP_Group class sets the dn for new
group as cn=newgroupname,ou=group,o=sb (the base DN part is converted
to lower case). This is fine but Horde refuses to show the new group
when a group list is requested - even though the newly created group
is also returned by the LDAP server. There is probably a better way
to fix this but I didn't do a lot od digging through the code.
I cannot reproduce this behavior.  Is it still a problem?
3.  Typo in the listAllUsers method in the Group_ldap class.
This has already been fixed in CVS.
11/27/2006 02:35:52 PM Chuck Hagenbuch Assigned to ben
State ⇒ Assigned
 
11/27/2006 11:22:09 AM ray (at) skyblue (dot) pty (dot) st Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Broken LDAP group management functionality
Queue ⇒ Horde Base
New Attachment: ldap.php.patch Download
State ⇒ Unconfirmed
Reply to this comment
The attached patch fixes the following issues I had with Horde and 
LDAP groups.



1.  The ldap_sort function appears to sort in alphabetical order, so 
the _nextGid method in the Group_ldap class often returns gidnumbers 
that already exist in the directory.



2. In the group configuration for my horde installation, I set the 
base DN as ou=Group,o=SB. When I create new groups, it appears that 
the LDAP_Group method in the LDAP_Group class sets the dn for new 
group as cn=newgroupname,ou=group,o=sb (the base DN part is converted 
to lower case). This is fine but Horde refuses to show the new group 
when a group list is requested - even though the newly created group 
is also returned by the LDAP server. There is probably a better way to 
fix this but I didn't do a lot od digging through the code.



3.  Typo in the listAllUsers method in the Group_ldap class.



Btw, the file modified by the patch is horde/lib/Horde/Group/ldap.php


Saved Queries