Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1237350

Summary: Setting lock screen in smart-card does not lock screen at all in KDE and locks in GNOME such that unlock has to be with power switch/reboot
Product: Red Hat Enterprise Linux 7 Reporter: Michael Moore <michael.moore>
Component: authconfigAssignee: Tomas Mraz <tmraz>
Status: CLOSED CANTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: ebenes, rstrode
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-01 17:36:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Moore 2015-06-30 21:53:31 UTC
Description of problem:

Smart card removal in KDE does not lock screen until timeout, but unlock requires smart card.

Smart card removal in Gnome blanks screen but unlock does not work, reporting insufficient credentials een though all other smart-card suthentications work.

Version-Release number of selected component (if applicable):
7.1 RHEL

How reproducible:
Seems to be consistent behavior

Steps to Reproduce:
1.log in with KDE-Plasma and smart card
2.Remove smart card--screen does not lock.
3.Log in with GNOME-Classic and smart card.  
4.Remove smart card and screen blanks
5.use mouse and smart card to attempt unlocking and an insufficient credentials appears when PIN is typed in.

Actual results:
Screen eventually locks in KDE, after the set idle time and NOW requires smart card to unlock
GNOME is unreachable--the only wakeup seems to be cold boot

Expected results:
KDE locks on card removal and requires smart card to unlock
GNOME locks scr3een on smart card removal and can be unlocked with smart card and PIN.
Additional info:

These examples are without the setting "Smart Card required"  The settings of that exhibit the same locking behavior as described except a root password for maintenance and an # authconfig --disablesmartcardrequired --update in single mode is necessary to restore a semblance of sanity.

Comment 2 Michael Moore 2015-06-30 22:13:31 UTC
GNOME does work properly and will unlock if one notices that it turns off the numlock and types the pin from the numeric keys on the keyboard instead of the pad.

Comment 3 Tomas Mraz 2015-07-01 07:29:41 UTC
These are two separate bugs and should be reported against the respective desktop components. Authconfig can hardly do anything with that.

Comment 4 Ray Strode [halfline] 2015-07-01 17:36:36 UTC
closing by request on bug 1238342 comment 0