[Tickets #4699] Broken LDAP group management functionality

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4699
-----------------------------------------------------------------------
 Ticket             | 4699
 Created By         | ray at skyblue.pty.st
 Summary            | Broken LDAP group management functionality
 Queue              | Horde Base
 Version            | 3.1.3
 Type               | Bug
 State              | Unconfirmed
 Priority           | 1. Low
 Owners             | 
+New Attachment     | ldap.php.patch
-----------------------------------------------------------------------


ray at skyblue.pty.st (2006-11-27 03:22) wrote:

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