6.0.0-beta1
7/6/25

[#15073] Read-only backends
Summary Read-only backends
Queue Turba
Queue Version 4.2.25
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester dpa-bugs (at) aegee (dot) org
Created 09/04/2021 (1401 days ago)
Due
Updated 09/09/2021 (1396 days ago)
Assigned
Resolved 09/09/2021 (1396 days ago)
Milestone
Patch No

History
09/09/2021 11:19:36 PM Michael Rubinsky Comment #2
State ⇒ Rejected
Priority ⇒ 1. Low
Reply to this comment
This should already be possible using the Administration->Permission system.

Please use the mailing lists to ask for further support.

http://www.horde.org/mail/ contains a list of all available mailing lists.
09/04/2021 07:53:46 AM dpa-bugs (at) aegee (dot) org Comment #1
State ⇒ New
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Read-only backends
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
Reply to this comment
I have integrated in Turba using backends.local.php an LDAP server.   
The server does not require authentication and the user cannot change 
anything on the server.  The data is read-only.

I want to be able to tell (in the configuration) that the backend is 
read-only, so that Turba does not offer the user contact editing.

Saved Queries