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 1937895

Summary:	SSSD update prompts for smartcard pin twice - After update to 7.9
Product:	Red Hat Enterprise Linux 9	Reporter:	cilmar <cilmar>
Component:	sssd	Assignee:	Sumit Bose <sbose>
Status:	CLOSED ERRATA	QA Contact:	Madhuri <mupadhye>
Severity:	medium	Docs Contact:
Priority:	high
Version:	9.0	CC:	aboscatt, atikhono, grajaiya, jhrozek, lslebodn, mzidek, pbrezina, sbose, sgadekar, spoore, thalman, tscherf
Target Milestone:	beta	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:	sync-to-jira
Fixed In Version:	sssd-2.7.0-1.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-15 11:17:22 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:

Comment 14 Alexey Tikhonov 2022-03-01 13:45:44 UTC

Upstream PR: https://github.com/SSSD/sssd/pull/6024

Comment 24 Alexey Tikhonov 2022-04-14 10:20:37 UTC

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

* `master`
    * 4d2277f8c3065771a8c3bbc7938309a4905640f0 - pam: better SC fallback message
    * 731b3e668c6a659922466aee7fa8093412707325 - pam: add more checks for require_cert_auth

Comment 36 Madhuri 2022-05-30 10:02:45 UTC

Verified manually without IPA server,

[root@ci-vm-10-0-137-60 external_ca]# rpm -qa sssd
sssd-2.7.0-2.el9.x86_64

Setup:
1. Install packages including softhsm
2. Create the conf file softhsm
3. Create temp cert/key to initialize virt_cacard slot
4. create virt_cacard service, start and enable it
5. Update sssd with match rule
6. Start # systemctl start pcscd virt_cacard sssd
7. Add local-user with expired cert.

Verification steps:
1. Install GDM packages
2. Here, we are using the expired cert, before login, get a login window with the message,
   'Please (re)insert (different) Smartcard'
3. After entering the pin, getting,
   'Sorry, smart card authentication didn't work. Please try again

The pin is not asking in the loop, giving the error message thus from this marking this as a verified.

Comment 42 errata-xmlrpc 2022-11-15 11:17:22 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-2022:8325