GNOME Bugzilla – Bug 107926
LDAP backend
Last modified: 2018-08-17 13:57:37 UTC
This will be a tracking bug for the LDAP backend. I didn't have time to work on this for a while, but the attached tarball does contain some working code. Using the attached README file and some knowledge of OpenLDAP, it shouldn't be difficult to set up and test. NOTE that the code spits lots of debugging info and certainly is not stable. I also tested the code with a remote server on a 100mbit network, it seems to work fine. Things which I still have to do: * support storing schemas in LDAP * support the locale stuff * support caching, though this also depends on some other things, like IPC between GConf daemons. So I think it makes more sense to put the caching code into the daemon itself (together with the IPC foo) and not in the backend. * we also need an on-disk cache for when we are offline, I guess this is also something for the daemon
Created attachment 14867 [details] README FIRST
Created attachment 14868 [details] The code.
future for now, but sooner is better...
Is anyone working on this?
A couple of thoughts on this: It's going to become very difficult to maintain the schema for lots of different configurations for lots of different components. LDAP supports an extensibleObject objectclass which basically allows you to turn off schema checking on a per-entry basis, but this is probably not an acceptable long term solution. It would be nice if there were a mechanism which allowed the "flexibility" of an XML DTD or schema to define your configuration schema in order to get some sort of schema checking without having to hack the LDAP server schema all the time or resort to a full blown online XML database. One strategy would be to have the gconf API write the configuration to _both_ the local file and LDAP at the same time (configurable, of course). That way, the local file becomes a cache, and configuration is robust w.r.t. network problems. The only problem here is that you need a good bi-directional sync mechanism, so that local changes can be sync'd up with the server and vice versa.
Heya, I'm working on an LDB backend. I'll base it off your schema, might as well make them compatibile.
GConf has been deprecated since 2011. GConf is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf/commits/master dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!