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 1845994 - GDM failure loop when no user mapped for smart card
Summary: GDM failure loop when no user mapped for smart card
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: sssd-qe
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-10 14:39 UTC by Alexey Tikhonov
Modified: 2020-11-04 02:09 UTC (History)
9 users (show)

Fixed In Version: sssd-2.3.0-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:05:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5190 0 None closed GDM password prompt when cert mapped to multiple users and promptusername is False 2020-11-01 15:57:43 UTC
Red Hat Product Errata RHBA-2020:4569 0 None None None 2020-11-04 02:05:42 UTC

Description Alexey Tikhonov 2020-06-10 14:39:56 UTC 
This bug was initially created as a copy of Bug #1551077

I am copying this bug because: to track fix for RHEL8



Description of problem:

When we have a smart card connected that contains certificates that are not mapped to a user, GDM login seems to fail with a repeated loop on either the PIN or User Hint Prompts:

"Sorry that didn't work.  Please try again."

This repeats in a loop.


Version-Release number of selected component (if applicable):
sssd-1.16.0-19.el7.x86_64


How reproducible:
Seems to be reproducible.

Steps to Reproduce:
1.  Setup IPA Env with Smart Card auth enabled.
2.  Add cert on card to user
3.  test
4.  remove certmapdata from user

Actual results:
failure loop


Expected results:
single failure and go back to normal login selection

Additional info:
Comment 1 Alexey Tikhonov 2020-06-10 14:41:58 UTC 
* `master`
    * 3ed254765fc92e9cc9e4c35335818eaf1256e0d6 - pam_sss: special handling for gdm-smartcard
    * 26c794da31c215fef3e41429f6f13afdaf349bee - pam_sss: add SERVICE_IS_GDM_SMARTCARD
Comment 3 Pavel Březina 2020-06-24 14:18:09 UTC 
Additional commit:

Pushed PR: https://github.com/SSSD/sssd/pull/5212

* `master`
    * 31e57432537b9d248839159d83cfa9049faf192b - pam_sss: make sure old certificate data is removed before retry
Comment 6 Scott Poore 2020-08-07 14:00:37 UTC 
Verified.

Version ::

sssd-client-2.3.0-7.el8.x86_64

Results ::

First confirm SC auth working:

[root@rhel8-8 yum.local.d]# su - ipauser1 -c 'su - ipauser1 -c whoami'
PIN for MyEID (sctest): 
ipauser1

Next remove certificate from ipauser1:

[root@rhel8-8 yum.local.d]# ipa user-mod ipauser1 --certificate=''
------------------------
Modified user "ipauser1"
------------------------
  User login: ipauser1
  First name: f
  Last name: l
  Home directory: /home/ipauser1
  Login shell: /bin/sh
  Principal name: ipauser1
  Principal alias: ipauser1
  Email address: ipauser1
  UID: 103000001
  GID: 103000001
  Account disabled: False
  Password: True
  Member of groups: ipausers
  Kerberos keys available: True
[root@rhel8-8 yum.local.d]# systemctl stop sssd; rm -rf /var/lib/sss/{db,mc}/*; systemctl start sssd
[root@rhel8-8 yum.local.d]# ipa certmap-match /root/usercert/ipauser1.crt
---------------
0 users matched
---------------
----------------------------
Number of entries returned 0
----------------------------

Now restart gdm and check behavior

[root@rhel8-8 yum.local.d]# systemctl restart gdm

After GDM comes back up, with card removed, I see username prompt.
Insert card, I see PIN prompt and not loop.
If I enter pin, it says "Sorry, that didn't work.  Please try again."

This is expected behavior with the fix.
Comment 9 errata-xmlrpc 2020-11-04 02:05:29 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 (sssd bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:4569
Note You need to log in before you can comment on or make changes to this bug.