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.
DescriptionAsha Akkiangady
2012-09-12 17:41:37 UTC
Description of problem:
SSO: Login to Virtual Terminal with in-correct kerberos password, enter user id again throws pam_pkcs11 error.
Version-Release number of selected component (if applicable):
gdm-2.30.4-33.el6_2.x86_64
authconfig-6.1.12-10.el6.x86_64
pam_pkcs11-0.6.2-12.1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Authentication is configured as:
Use smart card: ON Enforce smart card: OFF Log out behaviour configured to:
Activate screen saver.
2. System is configured to login with a smart card. Configured to perform pkinit to get Kerberos credential and ldap authentication. A smart card is enrolled for this user.
3. Restart the desktop.
5. This user is not in /etc/passwd file, but exists in ldap db.
4. User logs in using the tty virtual terminal screen e.g. <ctrl> + <alt> +
<F2>. User types correct user id.
5. The user is prompted for their kerberos password. Type something random.
6. Login incorrect message displayed, login prompt is re-displayed.
7. Type correct user id.
Actual results:
A message "ERROR:pam_pkcs11.c:310: load_pkcs11_module() failed:" displayed and ask for password.
Typing the correct password let the user log in successfully.
Expected results:
Error message should not be displayed. It should ask for password when user id is entered.
Additional info:
/var/log/secure has this:
Sep 12 13:41:00 dhcp231-57 login: argument card_only is not supported by this module
Sep 12 13:41:02 dhcp231-57 login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty2 ruser= rhost= user=kdcuser
Sep 12 13:41:02 dhcp231-57 login: pam_krb5[2574]: authentication fails for 'kdcuser' (kdcuser): Authentication failure (Decrypt integrity check failed)
Sep 12 13:41:05 dhcp231-57 login: FAILED LOGIN 1 FROM (null) FOR kdcuser, Authentication failure
Sep 12 13:41:07 dhcp231-57 login: argument card_only is not supported by this module
Sep 12 13:41:07 dhcp231-57 login: pam_pkcs11(login:auth): load_pkcs11_module() failed:
Sep 12 13:41:13 dhcp231-57 login: pam_krb5[2574]: error reading keytab 'FILE:/etc/krb5.keytab'
Sep 12 13:41:13 dhcp231-57 login: pam_krb5[2574]: TGT verified
Sep 12 13:41:13 dhcp231-57 login: pam_krb5[2574]: authentication succeeds for 'kdcuser' (kdcuser)
Sep 12 13:41:14 dhcp231-57 login: pam_unix(login:session): session opened for user kdcuser by LOGIN(uid=0)
Sep 12 13:41:14 dhcp231-57 login: LOGIN ON tty2 BY kdcuser
Comment 2RHEL Program Management
2012-12-14 08:07:16 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.