Summary | Endless loop in group permissions check |
Queue | Horde Framework Packages |
Type | Bug |
State | Resolved |
Priority | 3. High |
Owners | chuck (at) horde (dot) org |
Requester | rvs (at) angara (dot) ru |
Created | 2004-12-22 (5871 days ago) |
Due | |
Updated | 2004-12-31 (5862 days ago) |
Assigned | 2004-12-31 (5862 days ago) |
Resolved | 2004-12-31 (5862 days ago) |
Milestone | |
Patch | No |
State ⇒ Resolved
hasCapability('groups'). That should do it.
State ⇒ Assigned
Registry::hasMethod is removed from Auth_application::Auth_application but
Auth_application::hasCapability still invokes Registry::hasMethod.
New loop backtrack is:
Perms_datatree::hasPermission -> Perms_datatree::getPermissions ->
Group::singleton -> Auth_application::hasCapability ->
Registry::hasMethod -> Registry::_fillAPICache -> Registry::listApps
-> Registry::hasPermission -> Perms_datatree::hasPermission
Happy New Year! All the best wishes to you!!
State ⇒ Resolved
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 3. High
Summary ⇒ Endless loop in group permissions check
Queue ⇒ Horde Framework Packages
The Authentication driver is configured as application (IMP).
I have set up one group and filled it with user names.
Then I set up a permission to allow SHOW/READ access
to an application, for example, nag.
When I try to invoke nag an endless loop encountered and the browser
freezes until script exec timeout is run out.
The loop path/backtrace when the group permissions for the application
are checked is listed below:
Perms_datatree::hasPermission -> Perms_datatree::getPermissions ->
Group::singleton -> Auth::singleton -> Auth::factory ->
Auth_application::Auth_application -> Auth_application::_setParams ->
Registry::hasMethod -> Registry::_fillAPICache -> Registry::listApps
-> Registry::hasPermission -> Perms_datatree::hasPermission