Bug 242760

Summary: Need documentation for configuring a KDC to offer PKINIT services
Product: Red Hat Enterprise Linux 6 Reporter: Nalin Dahyabhai <nalin>
Component: doc-Security_GuideAssignee: Scott Radvan <sradvan>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Joshua Wulf <jwulf>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: ddomingo, k.georgiou, lcarlon, rlandman
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-16 03:36:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 181686, 547583    

Description Nalin Dahyabhai 2007-06-05 17:31:05 UTC
Description of problem:
While we ship the implementation, and the client setup procedure is covered by
the smart card client setup, there's additional configuration required on the
Kerberos KDC before it will offer clients the chance to use PKINIT.

Comment 2 Michael Hideo 2007-10-23 02:50:38 UTC
Removing automation notification

Comment 3 Don Domingo 2008-01-21 00:30:19 UTC
Hi Nalin,
please specify where this content should be added/revised (i.e. which book), and
please post the necessary client setup procedure. i don't have the equipment to
test this. thanks!

Comment 5 RHEL Program Management 2009-07-28 23:09:07 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 6 Scott Radvan 2010-02-23 23:52:38 UTC
Still NEEDINFO from reporter if this is to be added to the security guide

Comment 7 Scott Radvan 2010-04-16 03:36:18 UTC
closing with INSUFFICIENT_DATA as no response for so long