[Tickets #5253] Re: Marking an LDAP source as "read only"

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://dev.horde.org/horde/whups/ticket/?id=5253
-----------------------------------------------------------------------
 Ticket             | 5253
 Updated By         | Gunnar Wrobel <wrobel at pardus.de>
 Summary            | Marking an LDAP source as "read only"
 Queue              | Turba
 Version            | HEAD
 Type               | Enhancement
-State              | Feedback
+State              | Rejected
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


Gunnar Wrobel <wrobel at pardus.de> (2007-04-13 07:25) wrote:

> We removed just such a feature before because the permissions system 
> makes it redundant. 

Ah, okay.

> Why isn't the permissions system usable for Kolab  backends? I'd much
rather fix that instead.

Kolab does not use a database at all. And if somehow possible this should
remain that way. With the switch of the Share driver from the Datatree
backend to the Kolab IMAP server it is possible to run Horde without a db.
On the other hand there are packages like the Perms system that rely on the
datatree driver and thus on a db. So far this only resulted in a minor loss
of functionality. 

In the long run I certainly want to have either an LDAP based Perms driver
or an LDAP based datatree driver. But this currently does not have highest
priority. 

It is also fine if this remains a Kolab specific patch for now until I can
provide the necessary Perms driver. So I'll close this. Thanks for the
advice.