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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/2801

When checking for certificate on a smart card, if the first (of multiple) is revoked or expired, sssd should continue to check the other certificates for a valid one.

My understanding today is that if a smart card has multiple user certificates and the first is revoked or expired, no others are checked.  It would be nice to have all checked for a valid one to use.

Fixed upstream:
   * master: d0de7701d44c7a75210a9cb04634913ce3a94bfb
   * sssd-1-13: 6a1b214b4f17cd91afbcc8840caa65c875d52d3f

I am changing the bug status to FAILED_QA because of https://bugzilla.redhat.com/show_bug.cgi?id=1299994 and https://bugzilla.redhat.com/show_bug.cgi?id=1299998. 

gdm login and su using smartcard are working as expected, finding the valid cert from the card and successfully logging in.

I think FailedQA is not justified here because the ticket is about an issue in SSSD which is fixed.

Neither SSSD nor IPA can do anything about the issue in the OpenSSH client. Other ssh clients with Smartcard support might even work as expected. I would like to ask you to reconsider if this ticket can be set to verified.

Agreed, Sumit. This can be set as verified. Thanks for following on bz1299994.

Will verify this bug once there is a decision on https://bugzilla.redhat.com/show_bug.cgi?id=1299066

Marking this one verified.  Tests completed by Roshni earlier.  Was just waiting on bug #1299066 which is now verified.

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/RHBA-2016-0782.html