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.
Tested kerberos user smart card login using Gemalto 64K and CAC card with a Rhel 6 and Rhel 5.5 KDC. Smart card authentication succeeds and the kerberos credentials issued successfully on a i686 and x86_64 Rhel 6.0 Desktop.
Rpms from http://errata.devel.redhat.com/errata/show/10274 :
krb5-debuginfo-1.8.2-3.el6_0.3
krb5-pkinit-openssl-1.8.2-3.el6_0.3
krb5-workstation-1.8.2-3.el6_0.3
krb5-libs-1.8.2-3.el6_0.3
Steps:
1. Configured a Rhel 6 desktop to do smart card login. loaded up root certs onto
/etc/pki/nssdb.
2. Edit /etc/krb5.conf with the KDC and the client ticket details. Configure
krb5.conf with trust anchors, example:
pkinit_anchors = FILE:/etc/pki/nssdb/kdc-ca.pem
pkinit_cert_match = <KU>digitalSignature
3. yum install krb5-pkinit-openssl. Edit /etc/pam.d/smartcard-auth and
/etc/pam.d/system-auth to use pam_krb5 with
preauth_options=pkinit_identities=PKCS11:/usr/lib64/pkcs11/libcoolkeypk11.so
4. /etc/pki/nssdb/kdc-ca.pem contains CA certificates in base64 encoded format.
CA that issued smart card and CA that issued KDC certificate.
kdc-ca.pem on KDC also has these CA certificates.
5. Used the card to perform smart card login.
Logged in successfully and the kerberos credential is issued.
Marking this bug verified.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2010-0925.html