[Tickets #7481] Re: LDAP groups disappear inside perms
bugs at horde.org
bugs at horde.org
Thu Oct 23 17:56:59 UTC 2008
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/7481
------------------------------------------------------------------------------
Ticket | 7481
Updated By | horde_list at blomberg.tk
Summary | LDAP groups disappear inside perms
Queue | Horde Groupware Webmail Edition
Version | 1.2
Type | Bug
State | Duplicate
Priority | 2. Medium
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
horde_list at blomberg.tk (2008-10-23 13:56) wrote:
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.
More information about the bugs
mailing list