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 1538468 - [RFE]: allow smart card pin input before smart card is inserted
Summary: [RFE]: allow smart card pin input before smart card is inserted
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: sssd-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-25 07:19 UTC by adam winberg
Modified: 2020-05-02 18:55 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1724466 (view as bug list)
Environment:
Last Closed: 2020-03-18 09:50:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4647 0 None closed allow smart card pin input before smart card is inserted 2020-09-08 11:31:38 UTC
Github SSSD sssd issues 4670 0 None closed RFE: Require smartcard authentication 2020-09-08 11:31:38 UTC

Description adam winberg 2018-01-25 07:19:32 UTC 
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:
Comment 2 Sumit Bose 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?
Comment 3 adam winberg 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.
Comment 4 Jakub Hrozek 2018-01-31 21:27:48 UTC 
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3626
Comment 5 Jakub Hrozek 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.
Comment 6 Jakub Hrozek 2018-04-25 12:06:51 UTC 
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3650
Comment 10 Tomas Halman 2020-03-18 09:49:24 UTC 
This RFE has been implemented in Upstream and RHEL8. Considering RHEL 7 life-cycle this RFE will be not back-ported to RHEL 7
Note You need to log in before you can comment on or make changes to this bug.