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.
- Add feature to PKCS#11 pam module, smart card library. Have pam module
do pkinit on behalf of user in order to get initial Kerberos TGT.
- Currently the pam_pkcs11 module authenticates the user through the use
of smart cards but it does not do a pkinit and acquire a Kerberos TGT
for the authenticating user. The user would then have to acquire its TGT
by some other means. Having the pam module do the smart card
authentication as well as acquiring the Kerberos TGT would be ideal for
our environment.
---------------
1. Proposed title of this feature request
>
- Add feature to PKCS#11 pam module, smart card library. Have pam module
do pkinit on behalf of user in order to get initial Kerberos TGT.
2. Who is the customer behind the request?
- Lawrence Livermore National Lab
3. What is the nature and description of the request?
- Currently the pam_pkcs11 module authenticates the user through the use
of smart cards but it does not do a pkinit and acquire a Kerberos TGT
for the authenticating user. The user would then have to acquire its TGT
by some other means. Having the pam module do the smart card
authentication as well as acquiring the Kerberos TGT would be ideal for
our environment.
4. Why does the customer need this? (List the business requirements
here)
- Implementation of HSPD-12 smart card requirement. As well as ease of
use and configuration.
5. How would the customer like to achieve this? (List the functional
requirements here)
- Add feature to package for both rhel6, rhel7, and perhaps Fedoras.
6. For each functional requirement listed, specify how Red Hat and the
customer can test to confirm the requirement is successfully
implemented.
- The customer, LLNL, is prepared to test in it's environment in order
to verify new feature functional requirement.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
- Not known
8. Does the customer have any specific timeline dependencies and/or
which release would they like to target
- RHEL6, RHEL7, Fedoras
9. List any affected packages or components.
- pam_pkcs11
10. Would the customer be able to assist in testing this functionality
if implemented?
- Yes
The requested functionality is already in pam_krb. There is a project that is working on integrating all our authentication methods called sssd (though I don't think we have sssd for rhel 6).
This is a not a bug, but new feature request (for a feature we already support in a different way) so it's beyond the criteria for 6.9, so I'm closing wontfix.