Summary | Horde 3.0.7 and Group-Hooks infinite loop |
Queue | Horde Framework Packages |
Queue Version | FRAMEWORK_3 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | |
Requester | Thibault.LeMeur (at) supelec (dot) fr |
Created | 12/08/2005 (7153 days ago) |
Due | |
Updated | 12/17/2005 (7144 days ago) |
Assigned | |
Resolved | 12/10/2005 (7151 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
error on each login...
State ⇒ Resolved
than getGroupParents(). But I committed the other changes, thanks!
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Horde 3.0.7 and Group-Hooks infinite loop
Queue ⇒ Horde Framework Packages
New Attachment: Group_hooks.patch.txt
($conf['group']['driver'] = 'hooks').
Only one group is defined and used in the permission system to give
some users access to Ingo.
If a user is not in the "acces_ingo" group (provisionned with the
custom function (_group_hook_acces_ingo in config/hooks.php), then
Horde enters an infinite loop in its search for the user group
memberships:
* Group:userIsInGroup calls Group_Hooks:getGroupMemberships
* Group_Hooks:getGroupMemberships calls Group:userIsInGroup
We have found that a patch can be apply against the
"lib/Horde/Group/hooks.php" file:
* Avoid the infinite loop by replacing 2 calls of Group:userIsInGroup
by 2 calls of our custom group_hook function (since it is executed
only if hashook($group) is true)
* Replace the call of the non existent "getGroupParentList" method by
the call of the defined "getGroupParents" method instead
Please find attached the "# diff -u hooks.php hooks-patched.php" output.