0001404: wrong group uuid in sql table

Issue History
Date Modified	Username	Field	Change
2009-08-04 12:19	cweiss	New Issue
2009-08-04 12:19	cweiss	Status	new => assigned
2009-08-04 12:19	cweiss	Assigned To	=> lkneschke
2009-08-06 13:50	wvwebmaster	Issue Monitored: wvwebmaster
2009-08-18 16:33	wvwebmaster	Note Added: 0001298
2009-09-14 12:11	pschuele	Target Version	=> 2009-11 Milestone 2
2009-11-20 09:54	cweiss	Target Version	August (2009-11) Beta 1 => August (2009-11)
2009-11-26 14:45	pschuele	Target Version	August (2009-11) RC1 => 2010-03 Milestone 1
2010-01-15 17:17	pschuele	Target Version	2010-03 Milestone 1 => 2010-03 Milestone 2
2010-03-23 12:58	pschuele	Target Version	Mialena (2010-03) Milestone 2 => Mialena (2010-03) Beta 1
2010-03-23 14:24	wvwebmaster	Note Added: 0001984
2010-03-23 18:34	wvwebmaster	Note Edited: 0001984
2010-04-28 16:15	cweiss	Severity	minor => major
2010-04-30 17:08	cweiss	Status	assigned => resolved
2010-04-30 17:08	cweiss	Fixed in Version	=> Mialena (2010-03) Beta 1
2010-04-30 17:08	cweiss	Resolution	open => fixed

Notes
(0001298) wvwebmaster (reporter) 2009-08-18 16:33	i might found a resolution to this issue Tinebase/User/Ldap.php a user is searched with a filter like: $filter = "(&(objectclass=posixaccount)(" . sprintf($this->_queryFilter, $_filter) . "))"; Tinebase/Group/Ldap.php: a group is searched with a filter like: $filter = "(&({$this->_groupUUIDAttribute}=$groupId)(memberuid={$accountMetaData['uid']}))"; note the missing filter (objectClass=posixGroup)

(0001984) wvwebmaster (reporter) 2010-03-23 14:24 edited on: 2010-03-23 18:34	wieso wird der bug immer kurz vor release des target auf das naechste taget verschoben? ist der bug etwa nicht wichtig oder ist der ldap support in tine absichtlich auf diese starre art gebaut? das problem ist im foren thread eingehend beschrieben

Relationships