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 1371631 - login using gdm calls for gdm-smartcard when smartcard authentication is not enabled
Summary: login using gdm calls for gdm-smartcard when smartcard authentication is not ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: Steeve Goveas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 16:31 UTC by Roshni
Modified: 2020-05-02 18:28 UTC (History)
13 users (show)

Fixed In Version: sssd-1.14.0-42.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 07:20:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4198 0 None closed login using gdm calls for gdm-smartcard when smartcard authentication is not enabled 2020-12-17 12:05:40 UTC
Red Hat Product Errata RHEA-2016:2476 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2016-11-03 14:08:11 UTC

Description Roshni 2016-08-30 16:31:37 UTC 
Description of problem:
gdm calls for gdm-smartcard when smartcard authentication is not enabled

Version-Release number of selected component (if applicable):
gdm-3.14.2-18.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Install ipa-client and enable smartcard login using sssd by making the following change in sssd.conf

[pam]
pam_cert_auth = True

2. Trust the signing certs associated with the smartcard under /etc/pki/nssdb

3. Login using smartcard

4. Screen locks due to inactivity

5. login attempt prompts for pin

Actual results:
Auth fails

Expected results:
Auth should be successful

Additional info:

Seeing the following in /var/log/secure

Aug 30 11:48:00 dhcp129-53 gdm-smartcard]: pam_pkcs11(gdm-smartcard:auth): no valid certificate which meets all requirements found

/etc/dconf/db/distro.d/10-authconfig says enable-smartcard-authentication=false
Comment 1 Ray Strode [halfline] 2016-08-30 16:46:46 UTC 
How did you log in using smartcard if enable-smartcard-authentication=false ?

I think you must be missing steps in comment 0?
Comment 2 Roshni 2016-08-30 16:53:40 UTC 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/smart-cards.html#idm-smartcards-local
Comment 5 Sumit Bose 2016-08-31 11:45:25 UTC 
I might have an idea what is going on. For 7.3 I added a patch which set PKCS11_LOGIN_TOKEN_NAME when Smartcard authentication is used.

Ray, is it possible that the screen-saver will use gdm-smartcard whenever this environment variable is set without checking other options like the enable-smartcard-authentication dconf setting?

I'll prepare a test build which sets the variable only if SSSD was called from gdm-smartcard so that when gdm-password was used for the initial authentication, even with a Smartcard, the desktop components are not confused by the variable.
Comment 11 Jakub Hrozek 2016-08-31 15:31:29 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/3165
Comment 16 Jakub Hrozek 2016-09-16 13:18:53 UTC 
master:
 * 35ba922bc51416f02877b53a6f25c04104ae5f03
 * 3649b959709f1ab187092f054d4aace0798c98fa
 * 71cd9f98150577224559bdc12c53c01ce6f2c3d9
Comment 18 Roshni 2016-09-18 16:59:33 UTC 
[root@dhcp129-34 ~]# rpm -qi sssd
Name        : sssd
Version     : 1.14.0
Release     : 42.el7
Architecture: x86_64
Install Date: Sun 18 Sep 2016 12:54:23 PM EDT
Group       : Applications/System
Size        : 35147
License     : GPLv3+
Signature   : (none)
Source RPM  : sssd-1.14.0-42.el7.src.rpm
Build Date  : Fri 16 Sep 2016 09:48:09 AM EDT
Build Host  : x86-039.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://fedorahosted.org/sssd/
Summary     : System Security Services Daemon

Executed the steps in the bug description, authentication was successful while unlocking the screen.
Comment 19 Lukas Slebodnik 2016-09-19 11:17:42 UTC 
master:
* a8631161c47cbaefe7fd14b88202238bbdcc3dc8
Comment 21 errata-xmlrpc 2016-11-04 07:20:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2476.html
Note You need to log in before you can comment on or make changes to this bug.