Tickets :: Comment on [#4699] Broken LDAP group management functionality

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__ __ . . \|\/\|\|_/ \| \/ `\|\ \| \| \|\| \\|__/\__.\| \\|
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.
Attachment
Watch this ticket