RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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.

Okay i've created 3 system dbs

distro.d
site.d
local.d

distro.d is reserved for us, and the other two are for customers to use as they see fit.

*** Bug 1056072 has been marked as a duplicate of this bug. ***

Verified in dconf-0.16.0-6.el7

$ rpm -ql dconf
/etc/dconf
/etc/dconf/db
/etc/dconf/db/distro.d
/etc/dconf/db/distro.d/locks
/etc/dconf/db/local.d
/etc/dconf/db/local.d/locks
/etc/dconf/db/site.d
/etc/dconf/db/site.d/locks
...