Bug 1371321

Summary: 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.
Product: Red Hat Enterprise Linux 6 Reporter: Paul Gozart <pgozart>
Component: pam_pkcs11Assignee: Bob Relyea <rrelyea>
Status: CLOSED WONTFIX QA Contact: Asha Akkiangady <aakkiang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-22 22:33:25 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 Paul Gozart 2016-08-29 22:31:01 UTC 
- 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
Comment 2 Bob Relyea 2016-08-30 00:08:39 UTC 
pam_pkcs#11 passes the token and cert information to pam_krb which is supposed to do the pkinit. Is there a reason you can't use pam_krb?

bob
Comment 6 Bob Relyea 2016-09-22 22:33:25 UTC 
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.