| Summary: | Trying to login to desktop without a smart card shows blank screen when configured with smart card only option. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Asha Akkiangady <aakkiang> |
| Component: | pam_pkcs11 | Assignee: | Bob Relyea <rrelyea> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Asha Akkiangady <aakkiang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | jgalipea, jmagne, rpattath, rstrode |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pam_pkcs11-0.6.2-13.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 09:49:14 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: | |
|
Description
Asha Akkiangady
2013-11-26 20:58:35 UTC
right, there are two issues 1) card_only isn't a valid option to pass to pam_pkcs11 (should be fixed in authconfig) 2) pam_pkcs11 currently ignores the first argument should we just rebase to the latest upstream version or move the rhel6 patches forward? On pam_pkcs11-0.6.2-15.el7.x86_64 1. "Require smartcard for login" is enable in Sundry -> authentication -> Advanced options 2. in the login screen, if the card is removed it shows the list of users 3. Choose a local user 4. Prompts to insert the smart card 5. Smartcard is inserted 6. prompts for pin 7. pin is entered 8. Login fails twice and succeeds the third time On RHEL 6, if "Require smartcard for login" was enabled, irrespective of the smartcard is inserted or removed, the list of users are never listed on the login screen. It keeps prompting to insert the smartcard. honestly that sounds like a gnome-shell login screen bug. In theory you could have a user in the list that was associated with the smartcard, so asking for the pin isn't wrong. but what happens next is after a couple retries, it resets itself, notices the smartcard is inserted and then asks for the pin for the "right" user. that bug should probably be filed separately rather than failing qa for this bug filed a new bug based on comment 6 - https://bugzilla.redhat.com/show_bug.cgi?id=1063390 Verified this bug on pam_pkcs11-0.6.2-15.el7.x86_64 This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |