Bug 990630 - dconf should ship /etc/dconf/db/user and /etc/dconf/db/user.d and /etc/dconf/db/user.d/locks out of the box
dconf should ship /etc/dconf/db/user and /etc/dconf/db/user.d and /etc/dconf/...
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dconf (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Marek Kašík
Desktop QE
: 1056072 (view as bug list)
Depends On: 854724
Blocks: 872586 990625
  Show dependency treegraph
Reported: 2013-07-31 11:18 EDT by Ray Strode [halfline]
Modified: 2014-04-24 08:57 EDT (History)
6 users (show)

See Also:
Fixed In Version: dconf-0.16.0-3.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 990625
Last Closed: 2014-04-24 08:57:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ray Strode [halfline] 2013-07-31 11:18:34 EDT
+++ This bug was initially created as a clone of Bug #990625 +++

The new login screen does not have smartcard support. It needs to be added back for RHEL7.

--- Additional comment from Ray Strode [halfline] on 2013-07-31 10:56:20 EDT ---

So i've built a new gdm, gnome-settings-daemon, and gnome-shell that bring back the bulk of this support.  we're going to need some authconfig changes to, since we no longer read the same configuration database as before.

i'll file that as a separate bug.


We basically need to set the gsettings key:

org.gnome.login-screen enable-smartcard-authentication

to false if smartcard support is toggled off (default is enabled).

We also need to set the gsettings key:

org.gnome.login-screen enable-password-authentication

(and potentially enable-fingerprint-authentication) to false if forceSmartcard is configured.

Unfortunately, there's no way to set these keys globally and locked down using gsettings.  We'll have to drop files in /etc/dconf/db/gdm.d, /etc/dconf/db/gdm.d/locks, /etc/dconf/db/user.d, and /etc/dconf/db/user.d/locks then run dconf update.

First we need to change dconf to ship /etc/dconf/db/user.d by default. I'll file a separate bug for that.
Comment 1 Ray Strode [halfline] 2013-07-31 11:47:09 EDT
Okay i've created 3 system dbs


distro.d is reserved for us, and the other two are for customers to use as they see fit.
Comment 6 Marek Kašík 2014-01-23 08:16:05 EST
*** Bug 1056072 has been marked as a duplicate of this bug. ***
Comment 7 Jiri Koten 2014-04-24 08:57:15 EDT
Verified in dconf-0.16.0-6.el7

$ rpm -ql dconf

Note You need to log in before you can comment on or make changes to this bug.