[turba] turba permissions....

Marko Djukic marko at oblo.com
Wed Feb 26 17:37:17 PST 2003


Quoting Amith Varghese <amith at xalan.com>:

> I don't know if you saw my earlier post, but I kind of got around this by
> setting the admin of the personal address book as Auth::getAuth().  So maybe
> we
> don't need to do anything (maybe just need to comment sources.php.dist some
> more?)
yes i noticed, it works as each username returned by Auth::getAuth() will be
declared an admin for that turba source... i suppose it is a solution, but a bit
ugly to expect this php in the config files.

> I think you should let us know what your definition of public is... i think
> we
> can figure something out if we all have the same definition of "public"
i'd say it is a source which is available to be viewed/read by any user
regardless of login. a "personal" ldap would come under this definition i
suppose, if it is somehow handling all the auth and horde should not worry about
what the end user is. although i agree it is not exactly logical when comparing
the naming/settings values.

or maybe we need a setting to say that horde should not be checking perms? maybe
the public/readonly can be part of a perms array in the sources.php file:
'checkperms' => array('public' => true, 'readonly' => 'false')

so if the array is empty, as would be the case with personal ldap, perms would
not be checked. otherwise checkPermissions() would do its stuff based on the
elements of the array.
thoughts chuck?
m.


More information about the turba mailing list