[Koha-bugs] [Bug 28990] Allow changes for a configurable subset of systempreferences by superlibrarian only

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28990

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #8 from David Cook <dcook at prosentient.com.au> ---
(In reply to Fridolin Somers from comment #7)
> To add water in the mill :
> 
> I'd say if a preference is really system-related we should move it to
> koha-conf.xml.
> For example 'casServerUrl', it sounds system-related like LDAP
> authentication that is in koha-conf.xml.
> Idem for OPACBaseURL.

That's interesting.

On one hand, Donna makes the point that a library might not always have a
sysadmin available to make those changes via the CLI, so having them editable
by web UI is ideal. (From a deployment point of view, it might be nicer at
times to just make a data change via normal user activity in the UI rather than
needing to do a full deployment.)

On the other hand, as a vendor, there are times where I want to prevent all
library staff users (including superlibrarians) from making certain changes, as
they can break the system, make the system insecure, etc. 

--

What if we could add functionality for a sysadmin to lock system preferences
with all sysprefs defaulted to unlocked?

We could add a "locked" or "readonly" column to the systempreferences table. We
could then have a little CLI script for locking/unlocking system preferences,
setting system preference values.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.