Bug 747671 - Clean the wording around certificate authority chaining
Summary: Clean the wording around certificate authority chaining
Keywords:
Status: CLOSED DUPLICATE of bug 742611
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-20 17:49 UTC by Dmitri Pal
Modified: 2011-10-20 20:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-20 20:33:11 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dmitri Pal 2011-10-20 17:49:01 UTC
I think the customer read this from our manual:

"Alternatively, the IPA server can use a certificate issued by an external CA. This can be a corporate CA or a third-party CA like Verisign or Thawte. As with a normal setup process, using an external CA still uses a Dogtag Certificate System instance for the IPA server for issuing all of its client and replica certificates; the initial CA certificate is simply issued by a different CA.
When using an external CA, there are two additional steps that must be performed: submit the generated certificate request to the external CA and then load the CA certificate and issued server certificate to complete the setup. "

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Identity_Management_Guide/creating-server.html#install-ca-options

This is possible right? Maybe they misunderstood "external certificate" with "IPA without PKI". 


Suggestion: reword to talk about external "root" certificate and make the general wording a bit clearer to avoid the confusion.

Comment 1 Deon Ballard 2011-10-20 20:33:11 UTC

*** This bug has been marked as a duplicate of bug 742611 ***


Note You need to log in before you can comment on or make changes to this bug.