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.
Description of problem:
Authentication failure message even before attempting login using smartcard
Version-Release number of selected component (if applicable):
[root@dhcp129-54 ~]# rpm -q pam_pkcs11
pam_pkcs11-0.6.2-24.2.el7.x86_64
[root@dhcp129-54 ~]# rpm -q gdm
gdm-3.14.2-18.el7.x86_64
[root@dhcp129-54 ~]# rpm -q gnome-shell
gnome-shell-3.14.4-52.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. Modify authconfig to enable "Require smartcard for login"
2. Login using smartcard
3. Lock screen manually or due to inactivity
4. Remove smartcard
5. The login screen prompts to enter the smartcard
6. Click "Cancel" on the login screen
Actual results:
Before showing the message to insert the smartcard an authentication failure message is shown.
Expected results:
the login screen should show only the message to insert the smartcard
Additional info:
/var/log/secure
Sep 5 11:01:42 dhcp129-54 gdm-smartcard]: pam_pkcs11(gdm-smartcard:auth): conversation failed
Sep 5 11:01:42 dhcp129-54 gdm-smartcard]: pam_pkcs11(gdm-smartcard:auth): pam_get_pwd() failed: Conversation error
Sep 5 11:01:43 dhcp129-54 gdm-smartcard]: pam_pkcs11(gdm-smartcard:auth): conversation failed
Sep 5 11:01:43 dhcp129-54 gdm-smartcard]: pam_pkcs11(gdm-smartcard:auth): pam_get_pwd() failed: Conversation error
/var/log/messages
Sep 5 11:02:22 dhcp129-54 dbus-daemon: dbus[824]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Sep 5 11:02:22 dhcp129-54 dbus[824]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Sep 5 11:02:22 dhcp129-54 systemd: Starting Fingerprint Authentication Daemon...
Sep 5 11:02:22 dhcp129-54 dbus[824]: [system] Successfully activated service 'net.reactivated.Fprint'
Sep 5 11:02:22 dhcp129-54 dbus-daemon: dbus[824]: [system] Successfully activated service 'net.reactivated.Fprint'
Sep 5 11:02:22 dhcp129-54 fprintd: Launching FprintObject
Sep 5 11:02:22 dhcp129-54 fprintd: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Comment 4RHEL Program Management
2020-12-15 07:45:27 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.