[turba] Re: registry problem?
pete
pkarttun at siba.fi
Sat Aug 7 13:05:04 PDT 2004
No. Cookies are on and i've tested this with both mozilla and IE. I've noticed
this behaviour this far only in klutz,giapeto and orator. And i don't think
it's my permissions configuration problem either. giapeto has permissions
configured properly, Klutz and Orator have none. I've tracked the problem down
to the permissions check clause in pushApp - function which should give access
to app if no permissions are set:
(!Auth::isAdmin() && ($GLOBALS['perms']->exists($app) ?
!$GLOBALS['perms']->hasPermission($app,
Auth::getAuth(), PERMS_READ) :
!Auth::getAuth()))) {
Horde::logMessage(sprintf('User %s does not have READ permission
for %s', Auth::getAuth(), $app), __FILE__, __LINE__, PEAR_LOG_DEBUG);
return PEAR::raiseError(sprintf(_("User %s is not authorised for %
s."), Auth::getAuth(), $this->applications[$app]['name']), 'permission_denied');
}
Without trying to debug the mechanisms here, i quickly tried to downgrade the
if-clause to the one in Registry.php revision 1.192:
if ($checkPerms &&
(!Auth::isAdmin() && $GLOBALS['perms']->exists($app) &&
!$GLOBALS['perms']->hasPermission($app, Auth::getAuth(),
PERMS_READ))) {
Horde::logMessage(sprintf('User %s does not have READ permission
for %s', Auth::getAuth(), $app), __FILE__, __LINE__, PEAR_LOG_DEBUG);
return PEAR::raiseError(sprintf(_("User %s is not authorised for %
s."), Auth::getAuth(), $this->applications[$app]['name']),
'permission_denied');
}
... and it helped for Orator and Klutz! Every app except giapeto - when moving
blocks - seems to work fine now.
:pete
>Quoting pete <pkarttun at siba.fi>:
>
>> When i'm adding a client from turba addressbook in nag and click
>> "Cancel" i'll
>> be redirected to login page. The login session is not destroyed
>> however and i'm
>> able to come back to the previous page by clicking "Back" in my browser. The
>> redirection happens in the turba/base.php in:
>
>Do you have cookies turned off? I take it you can use both nag and turba
>normally with the user you got this behavior with logged in? Obviouly Horde
>thinks you lack permissions somehow, so either the session is getting lost or
>you haven't configured permissions correctly.
>
>-chuck
>
>--
>"Regard my poor demoralized mule!" - Juan Valdez
>
>
More information about the turba
mailing list