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.
Bug 1134518 - [Doc] [RFE] add option to have certmonger add IPA CA cert to NSS database
Summary: [Doc] [RFE] add option to have certmonger add IPA CA cert to NSS database
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-System_Level_Authentication_Guide
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 7.1
Assignee: Aneta Šteflová Petrová
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On: 767700
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-27 16:30 UTC by Tomas Capek
Modified: 2019-03-06 01:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 767700
Environment:
Last Closed: 2017-02-21 16:07:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomas Capek 2014-08-27 16:30:15 UTC 
+++ This bug was initially created as a clone of Bug #767700 +++
+++ This bug was initially created as a clone of Bug #759545 +++

Description of problem:

It would be handy if ipa-getcert could have a option to fetch and install the IPA CA certificate into an NSS database when issuing a request.

This CA cert should be available locally in /etc/ipa/ca.crt for enrolled hosts or on the IPA server in /ipa/config/ca.crt (can be retrieved over HTTP).

--- Additional comment from nalin on 2011-12-02 15:02:15 EST ---

What would be the expected behavior in cases when the certificate and private key for a request were being stored in a flat file?

Most of the time the IPA CA certificate doesn't contain a friendlyName extension, so ipa-getcert would need to be told where the database is and which nickname to set for the CA certificate in the database.  At that point, what's the advantage of having ipa-getcert or certmonger do it instead of running certutil?

--- Additional comment from rcritten on 2011-12-02 15:27:35 EST ---

This would be for NSS databases only, flat file users are on their own.

The nickname format is '$REALM IPA CA'

ipa-getcert should already know the database location, right?

I think requested advantage is saving the user a step

You may be able to get away with documenting this in the man page.

--- Additional comment from dpal on 2011-12-03 13:17:25 EST ---

If it saves the step - great. Seems like an improvement to me that will save people time.
Comment 3 Aneta Šteflová Petrová 2017-02-21 16:07:38 UTC 
This request is very old and I'm not aware of any corresponding doc plan item. I'm closing this BZ.

If you don't agree with this decision, feel free to reopen it.
Note You need to log in before you can comment on or make changes to this bug.