Mon, 06 Apr 2026 01:10:01 +0000 https://bugs.horde.org/ticket/7481 LDAP groups disappear inside perms I've a fully working horde groupware webmail installation. User and groups are pulled from LDAP and all users/groups are found. I can add a group to the calendar perms of my personal calendar. But after logout/login the group disappears from the permissions list. The same works with ldap users. A little debugging revealed that the gorup id gets somewhere changed to "0". Inside the data table kronolith_shares_groups it's correctly recorded with cn=... It happens with DataTree and SQL as Permission drivers. Sun, 12 Oct 2008 13:11:04 +0000 https://bugs.horde.org/ticket/7481#t49628 Duplicate of bug #6883. Sun, 19 Oct 2008 16:56:50 +0000 https://bugs.horde.org/ticket/7481#t49788 I have the same problem. With Horde 3.3 and group_uid field as varchar according to the solution for bug #6883. The group id (cn=...) is correctly set in the table nag_shares_groups (this requires that the datatype is changed from integer to varchar). It seems that the group_uid is casted to int in _getShareCriteria at line 673 in framework/Share/Share/sql.php rev. 1.1.2.47. I don't understand how an LDAP group id (cn=...) should be casted to int. This is a typical error-log: Oct 23 19:12:56 HORDE [error] [nag] MDB2 Error: unknown error: _doQuery: [Error message: Could not execute statement] [Last executed query: SELECT DISTINCT s.* FROM nag_shares s LEFT JOIN nag_shares_users AS u ON u.share_id = s.share_id LEFT JOIN nag_shares_groups AS g ON g.share_id = s.share_id WHERE s.share_owner = 'jbl' OR (s.perm_creator & 4) != 0 OR (s.perm_default & 4) != 0 OR ( u.user_uid = 'jbl' AND (u.perm & 4) != 0) OR (g.group_uid IN (0,0,0,0,0) AND (g.perm & 4) != 0) ORDER BY s.attribute_name ASC] [Native message: ERROR: IN types character varying and integer cannot be matched] [pid 25224 on line 457 of "/usr/local/www/horde/lib/Horde/Share/sql.php"] I do not think this is a duplicate of bug #6883. Thu, 23 Oct 2008 17:56:59 +0000 https://bugs.horde.org/ticket/7481#t49912 > I do not think this is a duplicate of bug #6883. Of course it is. But the fix for bug #6883 has been incomplete because no one who reported it bothered to test our fixes. Thu, 23 Oct 2008 21:18:54 +0000 https://bugs.horde.org/ticket/7481#t49920