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 was initially created as a clone of Bug #1538468 +++
Description of problem:
Using pam_pkcs11, I can input my smart card PIN code in GDM (login/unlock) before smart card is inserted. When smart card is inserted my previously entered pin code is used.
Using sssd (pam_sss) instead of pam_pkcs11 this does not work, I have to wait for the smart card to be recognized before I can enter the PIN.
This is a little thing, but coming from pam_pkcs11 it is an annoyance and often an interruption in workflow. Seeing as pam_pkcs11 is deprecated and wont be available in RHEL8 it would be nice to have the same features available in sssd.
Version-Release number of selected component (if applicable):
sssd-1.15.2-50.el7_4.8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Configure sssd/pam_sss for use with smartcard
2. Reboot/log out to GDM login screen
3.
Actual results:
You have to wait for card to be read before pin prompt is available.
Expected results:
I'd like the pin prompt to be available for input regardless if smartcard is read or not. If I input the PIN and press enter, I expect my input to be used as soon as smartcard is recognized (a sensible TTL for this might be a good idea).
Additional info:
--- Additional comment from Sumit Bose on 2018-01-25 09:04:42 UTC ---
Thank you for opening this ticket and https://bugzilla.redhat.com/show_bug.cgi?id=1538464.
I already have the 'wait_for_card' option on my todo list but it is always good to have a ticket to track this.
I'm just wondering where you see the difference between the two tickets? Do you have different work-flows or use-cases in mind here?
--- Additional comment from adam winberg on 2018-01-25 11:42:11 UTC ---
Yeah, I know you are working on it but I also felt it was nice to have somewhere for me to track that progress.
As for the two tickets - this one is about a behaviour thats manifestating in the gdm login/unlock screen, and the other is about behaviour in a console/tty login. The latter I am pretty certain is connected to the 'wait_for_card' parameter in pam_pkcs11, but I actually didnt think of the possibility that this ticket could also be solved by that same functionality.
So, if the 'wait_for_card' functionality is the key to 'solving' both these tickets then it seems redundant and I agree that they should be combined into one single ticket.
--- Additional comment from Jakub Hrozek on 2018-01-31 21:27:48 UTC ---
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3626
--- Additional comment from Jakub Hrozek on 2018-01-31 21:30:07 UTC ---
I've linked both bugzilla tickets to a single upstream ticket for now. That way, when the wait_for_card option is implemented, we can ask for testing of that option and decide whether we want a separate upstream ticket for the TTY bug as well or not.
--- Additional comment from Jakub Hrozek on 2018-04-25 12:06:51 UTC ---
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3650
Hi,
I re-read your original request and I agree that it is not matched by the current behavior of the 'require_cert_auth' option. While I agree that it might be convenient to enter the PIN first and then search the Smartcard and insert it into the reader I think the behavior of pam_pkcs11 is quite risky and I'd prefer to not copy it in SSSD. If someone types in a wrong PIN and leave caps-lock enabled your Smartcard will first see the wrong PIN and when you type the right PIN it will be in upper-case, so your bad pin counter will be already on 2. Depending on the settings of the Smartcard it might be already locked.
Please let me know if there are other use-cases for this feature, otherwise I'd prefer to close this ticket.
bye,
Sumit
(In reply to adam winberg from comment #5)
> ok, i have no other use cases so you can close this.
Hi,
thanks for your feedback and understanding.
bye,
Sumit