Bug 759545

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?

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.

If it saves the step - great. Seems like an improvement to me that will save people time.

This step was not well documented in the manual procedure and users stumbled on it.

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

re-opening

This should be more or less sorted in 0.75.x, with getcert's -a and -F flags, and more broadly via the "root-cert-files" and "root-cert-nssdbs" and related properties on both enrollment requests and on CAs.

certmonger-0.75.14-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/certmonger-0.75.14-1.fc21

certmonger-0.75.14-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/certmonger-0.75.14-1.fc20

Package certmonger-0.75.14-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing certmonger-0.75.14-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-10127/certmonger-0.75.14-1.fc21
then log in and leave karma (feedback).

certmonger-0.75.14-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

certmonger-0.75.14-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.